If the customer is using a Direct Connect Private VIF to terminate the Direct Connect on the Virtual Gateway in their VPC:
- For receiving new CIDR range on-premise, AWS would send new CIDR range in the next BGP update on the DX VIF session to customer's router. Customer does not have to make any config change.
If the customer is using a Direct Connect Transit VIF to terminate the Direct Connect on Transit Gateway:
- They may need to modify the prefixes in Transit Gateway on the Direct Connection attachment to send the new range (100.x.x.x) to on premises.
- If automatic route propagation from the VPC attachment is enabled then the 100.x.x.x route will appear in Transit Gateway automatically.
- If automatic route propagation from the VPC attachment is disabled then the customer will need to add the 100.x.x.x route manually.
On premises the customer will need to ensure that the 100.x.x.x route is accepted and added to any local routing protocols (static or dynamic).
VPC and Subnets CIDR Best Practices?asked 3 days ago
Amazon Managed Workflows for Apache Airflow (MWAA) VPC RequirementsAccepted Answerasked 2 years ago
VPC/CIDR IPv4 issueasked 4 months ago
Direct Connect Hide VPC CIDR Blocks from BGP PeerAccepted Answerasked 3 years ago
Reserved CIDR range in a SubnetAccepted AnswerMODERATORasked 2 years ago
What will Route53 do if client ip matches multiple CIDR blocks in different CIDR Locations?asked 3 months ago
Cloudformation - Update CIDR Range in Stack WITHOUT Terminating All RDS, ELB's InstancesAccepted AnswerMODERATORasked 4 years ago
S2S VPN host address within CIDR range of VPC (10.0.0.0/16)Accepted Answerasked a month ago
Secondary CIDR VPC block - Direct ConnectAccepted Answerasked 4 years ago
Is the Overlay IP CIDR range for SAP on AWS just a secondary CIDR range added to same VPC?Accepted Answerasked 9 days ago