Cloudformation-coverage-roadmap: AWS::EC2::TransitGatewayAttachment - Support for TGW Peering

[be-meyer]

Currently the AWS::EC2::TransitGatewayAttachment doesn't allow to initialise a peering to a different TGW.

2. Scope of the Request

Both of them is acceptable:

• new attribute for an existing resource is desired
• new option for an existing attribute is desired

Example

One of {VpcId, SubnetIds} or {PeerTgwId} is required.

Type: AWS::EC2::TransitGatewayAttachment
Properties: 
  SubnetIds: 
    - String?
  Tags: 
    - Tag
  TransitGatewayId: String
  VpcId: String?
  PeerTgwId: String?

Sample

Type: AWS::EC2::TransitGatewayAttachment
Properties: 
  Tags: 
    - Key: Name
      Value: MyPeeringAttachment
  TransitGatewayId: tgw-123456789
  PeerTgwId: tgw-987654321

3. Expected behavior

Any particular or uncommon Delete behavior? What are the expected options?

• The peering connection need to be deleted before deletion of the transit gateway to prevent form DELETE_FAILED Transit Gateway tgw-xyz did not stabilize. errors when deleting the stack.

4. Suggest specific test cases

5. Helpful Links to speed up research and evaluation

• CLI command to initialize a new peering attachment: https://docs.aws.amazon.com/cli/latest/reference/ec2/create-transit-gateway-peering-attachment.html

6. Category (required)

Networking & Content (VPC, Route53, API GW,...)

7. Any additional context (optional)

[gogonaft]

+1 for need of TGW Peering in CF

[nammireddy]

+1 for support of TGW Peering in CloudFormation

[plinioh]

+1 for support of TGW Peering in CloudFormation

[predrag044]

+1 for support of TGW Peering in CloudFormation

[benbridts]

@gogonaft @nammireddy @plinioh @predrag044

• 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