aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
AWS::EC2::Instance should apply tags to created volumes
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
## 2. Scope of request
The documentation states that "The specified tags are applied to all instances or volumes that are created during launch" but this is not the case.
## 3. Expected behavior
Specifying tags on `AWS::EC2::Instance` should tag the instance and all created volumes.
## 5. Helpful Links to speed up research and evaluation
Docs: https://docs.aws.amazon.com/en_pv/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-instance.html#cfn-ec2-instance-tags
Support: https://aws.amazon.com/premiumsupport/knowledge-center/cloudformation-instance-tag-root-volume/
## 6. Category (required) - Will help with tagging and be easier to find by other users to +1
1. Compute (EC2, ECS, EKS, Lambda...)
Contributor guide
Research direction
Start with the linked CloudFormation EC2 Instance Tags documentation and AWS Support article; the payload names no repository files, tests, or entry points. Confirm the documented behavior for AWS::EC2::Instance tags and created volumes, then establish what repository change or coverage update would record the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 30/100