as title says, i’ve a function with a trigger on S3 using the new definition:
functions: lambda: handler: src/handler.handler events: - s3: bucket: bucketName event: s3:ObjectCreated:* rules: - prefix: xml-texts/ - suffix: .xml existing: true
The bucket already exists and i’m using the
existing: true to avoid the error as described in
I’ll put my cloudFormation json too: https://pastebin.com/8v6GhunX
Is this a feature? a bug? someone knows why this happens?