Elastic Beanstalk creates a shared S3 bucket without option to link to a pre-existing bucket

[david-w-webb]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave "+1" or "me too" comments. They generate extra noise for issue followers and do not help prioritize the request.

Requesting the option to link an Elastic Beanstalk Environment a pre-created S3 bucket of my choice instead of using the default bucket created by Elastic Beanstalk.

Currently, when the first Elastic Beanstalk environment is deployed to an account, it creates S3 bucket: elasticbeanstalk-${AWS::Region}-${AWS::AccountId}. This bucket is used to store all artifacts from any Elastic Beanstalk environment.

Note: Elastic Beanstalk environments are able to specify separate, pre-created logging buckets for CloudWatch logs.

In a shared, multi-tenant AWS account, different teams need to be able to use different S3 buckets for:

• Security (who can edit your application)
• Cost management (tagging)