...

Timeline

• We expect to complete all stages in the Preparation phase in December 2022.
• We expect to complete all stages in the Migration phase in January 2023.
• More specific dates for each stage are forthcoming.

FAQs

How do I tell if my AWS account will be affected by this change?

How will this change affect my AWS account costs?

Does this change affect VPC peering?

VPC peering is not affected by this change.

However, since the Transit Gateway in the v2 architecture is configured to fully interconnect attached VPCs, most if not all VPC peering could be removed. When VPC peering is removed, VPC-to-VPC traffic that formerly used a peering connection would use the Transit Gateway instead. All traffic would remain in AWS, and the traffic would take two (2) hops to reach the target VPC instead of the one (1) hop that the peering connections support.

 There is one case where VPC peering would need to remain in place. When Security Groups in a VPC reference Security Groups in a peered VPC, that peering cannot be removed without adjusting the security group to use CIDR blocks instead of the referenced Security Group. TGW Attachments do not support this type of Security Group referencing.

Reducing the amount of peering amongst Cornell AWS VPCs will take place later and customers will be contacted separately about that. No peering changes are planned as part of the Direct Connect architecture migration.

When, specifically, will this migration occur?

• We expect to complete all stages in the Preparation phase in December 2022.
• We expect to complete all stages in the Migration phase in January 2023.
• More specific dates for each stage are forthcoming.

What if I use Terraform or a similar tool to manage the network resources in my AWS account?

References

• 2022-11-02 Upcoming AWS Direct Connect Changes

...