Following this article here I fixed the bug by adding a Custom Resources which adds the Notification trigger after Bucket and Lambda creation (see here).
None of the other resolutions are appropriate:
omitting SourceArn in the LambdaPermission --> it's not a least privilege approach
or using BucketPrefix instead of the ConfigurationBucketName parameter --> This would take away the flexibility to use an existing bucket with a fixed name
@RemekHet
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
*Issue #, if available: #1
*Description of changes:
Following this article here I fixed the bug by adding a Custom Resources which adds the Notification trigger after Bucket and Lambda creation (see here).
None of the other resolutions are appropriate:
BucketPrefixinstead of theConfigurationBucketNameparameter --> This would take away the flexibility to use an existing bucket with a fixed name@RemekHet
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.