Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS::S3::Bucket NotificationConfiguration - Add support for existing buckets #466

Closed
TonyFNZ opened this issue May 6, 2020 · 3 comments
Closed

Comments

@TonyFNZ
Copy link

TonyFNZ commented May 6, 2020

1. Title

AWS::S3::Bucket NotificationConfiguration - Add support for existing buckets

2. Scope of request

AWS::S3::Bucket NotificationConfiguration can only be set in the CFN template that created the target S3 bucket. A new resource type should be created so that NotificationConfiguration can be updated on an existing bucket.

3. Expected behavior

There is an existing CloudFormation Custom Resource (see link below) which supports this usecase, however a new resource type should be added so that it is possible to do this in vanilla CloudFormation without requiring the clutter of having lots of custom resources defined.

Ideally this resource would not overwrite other notification configuration which already exists on the target bucket.

4. Suggest specific test cases

This will allow Lambda functions to be created and subscribed to S3 events without requiring the Lambda function and notification configuration to be defined in the same template as the target S3 bucket.

5. Helpful Links to speed up research and evaluation

Existing Custom Resource which implements this functionality
https://aws.amazon.com/premiumsupport/knowledge-center/cloudformation-s3-notification-lambda/

CDK issue which is blocked by this issue: aws/aws-cdk#4323

6. Category

  1. Storage (S3, EFS, Backup...)
@purnesh
Copy link

purnesh commented May 6, 2020

+1

@benkehoe
Copy link
Contributor

benkehoe commented May 6, 2020

This has already been raised as issue #79. It's a problem that notification configuration isn't a separate resource even when the bucket is in the same stack.

@TonyFNZ
Copy link
Author

TonyFNZ commented May 7, 2020

Thanks @benkehoe. I tried to search for existing issues, but didn't find that one. Closing this as duplicate

@TonyFNZ TonyFNZ closed this as completed May 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants