AWS vpc documentation change
Summary
Expanded CIDR conflict documentation to include overlapping ranges in transit gateway VPC attachments
Security assessment
Clarifies routing limitations but does not address a specific security vulnerability or introduce security features
Diff
diff --git a/vpc/latest/tgw/tgw-vpc-attachments.md b/vpc/latest/tgw/tgw-vpc-attachments.md index 8986bdd14..1a7a7c4c7 100644 --- a/vpc/latest/tgw/tgw-vpc-attachments.md +++ b/vpc/latest/tgw/tgw-vpc-attachments.md @@ -17 +17 @@ An Amazon Virtual Private Cloud (VPC) attachment to a transit gateway allows you - * A transit gateway doesn't support routing between VPCs with identical CIDRs. If you attach a VPC to a transit gateway and its CIDR is identical to the CIDR of another VPC that's already attached to the transit gateway, the routes for the newly attached VPC aren't propagated to the transit gateway route table. + * A transit gateway doesn't support routing between VPCs with identical CIDRs, or if a CIDR in a range overlaps a CIDR in an attached VPC. If you attach a VPC to a transit gateway and its CIDR is identical to, or overlaps with, the CIDR of another VPC that's already attached to the transit gateway, the routes for the newly attached VPC aren't propagated to the transit gateway route table.