TransitGatewayAttachment vs TransitGatewayVpcAttachment?
Looking at the documentation of AWS::EC2::TransitGatewayAttachment and AWS::EC2::TransitGatewayVpcAttachment it looks that first is a subset of later. If TransitGatewayVpcAttachmentis kept only for backwards compatibility, would it make sense to add a note into documentation stating this is obsolete version, and there is better alternative available?
- 新しい順
- 投票が多い順
- コメントが多い順
Hello, I understand that AWS::EC2::TransitGatewayAttachment and AWS::EC2::TransitGatewayVpcAttachment look very similar, so here is an explanation of the difference between these 2 templates.
For AWS::EC2::TransitGatewayAttachment, the use case it to attach a specified VPC to a Transit Gateway. This CloudFormation template cannot be used for adding or removing subnets after having a already established attachment, as it will error out. For this reason, it is better suited for creation of the attachment the first time around.
For AWS::EC2::TransitGatewayVpcAttachment, the use case is to specify a certain attachment. This CloudFormation resource will be able to update already established VPC & Transit Gateway connection's Subnets, without having to delete and create an entirely new attachment. For this case, updating the attachment would be preferred.
The link below talks about the implementation of each Template and issues that other users have faced. Please note while this is the official AWS CloudFormation GitHub repository, any user with an account can post, even if they are unaffiliated with AWS.
- Reference (Please note this is the official AWS CloudFormation GitHub but any user can post replies): https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/327
