aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
Add S3 Bucket names as an AWS Specific Parameter
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
AWS::S3::Bucket
### Resource name
_No response_
### Description
This request is similar to #1380.
When building CloudFormation templates for use by others we must ask users to track down and then copy-and-paste S3 bucket names in the active account. A more convenient way to handle this would be to add `AWS::S3::Bucket` resources as an [AWS-specific parameter type](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/parameters-section-structure.html#aws-specific-parameter-types).
The desired enhancement would include:
- Automatically populating S3 bucket names in a stack parameter drop-down when the user is installing the CloudFormation template via the AWS Console.
- The parameter drop-down for S3 bucket names should be searchable.
- Validation of the parameter string value to be either a valid S3 bucket name or ARN.
- Validation of the specified S3 bucket's existence when attempting to deploy the stack.
### Other Details
_No response_
Contributor guide
Research direction
Start by reviewing issue #1380 and the linked AWS CloudFormation AWS-specific parameter documentation. Done means S3 bucket resources can populate a searchable console parameter drop-down, accept a valid bucket name or ARN, and validate that the bucket exists during stack deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100