aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
AWS::Batch resources don’t receive the aws:cloudformation built-in tags / default AutoTags
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
AWS::Batch::ComputeEnvironment
### Resource name
_No response_
### Description
Neither AWS::Batch::ComputeEnvironment nor AWS::Batch::JobQueue receive the built-in CloudFormation stack tags:
- aws:cloudformation:logical-id
- aws:cloudformation:stack-id
- aws:cloudformation:stack-name
This makes it vary hard to trace resources back to the stack that created them. Considering the 50 Compute Environment per account/region hard quota, this makes it hard for users to identify the source of CE's when deciding which to remove to stay under the quota.
These tags should be propagated to ALL resources which support tags.
### Other Details
_No response_
Contributor guide
Research direction
The issue names AWS::Batch::ComputeEnvironment and AWS::Batch::JobQueue as affected resources. Start by checking how CloudFormation built-in stack tags and default AutoTags are handled for tag-supporting resources; done means both resources receive the listed aws:cloudformation tags, with propagation covering all supported resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100