1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
0
Expanding on the comment by @mike, your small files would be uploaded in one piece whereas large ones (over 5MB) would be multi-part uploads that are different API calls. So depending how you defined your trigger conditions you could be picking up one but not the other.
I just used the web-interface to set it up. There is no option to define any wildcards. https://paste.pics/FRKFU
When looking at the trigger details (within the lambda function's trigger configuration) it just says: "Event type: ObjectCreated"
Contenido relevante
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace 3 años
- OFICIAL DE AWSActualizada hace 7 meses
Is the event you're listening for "s3:ObjectCreated:*", specifically with the wildcard on the end?
I just used the web-interface to set it up. There is no option to define any wildcards. https://paste.pics/FRKFU
When looking at the trigger details (within the lambda function's trigger configuration) it just says: "Event type: ObjectCreated"
For the sake of completeness I added a second trigger for the Multipart Upload (see screenshot). As assumed there was no change in behavior: https://paste.pics/FRKRU As stated I am using an AWS KMS managed customer master key (SSE-KMS) on the bucket and for the upload
Does the lambda function need the "AmazonS3ReadOnlyAccess" Policy to allow invocation via S3 multipart upload trigger?