aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
AWS::EC2::EgressOnlyInternetGateway - Tags
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
## 1. Title
AWS::EC2::EgressOnlyInternetGateway-Tags - set Tags via CloudFormation
## 2. Scope of request
We're using Egress only Internet Gateways extensively, so we have more than one per-region. Currently you only can set the VPC and nothing else when using CloudFormation while it's possible to add Tags on the web console. It would be easier if we can add Tags to the EIGW from the CFn itself like we can add Tags to the "plain" Internet Gateways. If we can add Name tags then we can easily distinguish the EIGWs from each other.
```json
"MyEgressOnlyInternetGateway": {
"Properties": {
"Tags": [
{ "Key": "Name", "Value": "myeigw" }
],
"VpcId": { "Ref": "MyVPC" }
},
"Type": "AWS::EC2::EgressOnlyInternetGateway"
}
```
## 3. Expected behavior
Set the Tags.
## 4. Suggest specific test cases
N/A
## 5. Helpful Links to speed up research and evaluation
N/A
## 6. Category
Networking
## 7. Any additional context
N/A
Contributor guide
Research direction
Start by reviewing the AWS::EC2::EgressOnlyInternetGateway resource definition and the existing plain Internet Gateway tag behavior referenced in the issue. Confirm how Tags should work alongside VpcId, then verify the supplied CloudFormation example; completion means Tags, including a Name tag, are accepted and applied, though the issue names no repository files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100