Warning |
---|
This documentation is in transition. It is be cannibalized to create new, final documentation about the v2 Direct Connect Architecturepage is being retained for historical purposes, but is no longer maintained. All relevant Direct Connect information about the current (2023 and after) Direct Connect architecture has been migrated to primary customer Direct Connect documentation, Cornell AWS Direct Connect. |
Info |
---|
Executive Summary
|
Table of Contents |
---|
...
Introduction
Excerpt |
---|
This document provides details about the Direct Connect architecture migration Cornell will be executing in early 2023. |
Rationale
Cornell AWS accounts using Direct Connect for private access to Cornell networks will be transitioned to using Internet 2 Cloud Connect (I2CC) as the Direct Connect provider.
The Internet 2 Direct Connect provider offers several benefits:
- Consolidating and simplifying configuration and management of Direct Connect for Cornell AWS accounts
- Improving flexibility and bandwidth of Direct Connect connectivity
- Allows private Cornell network traffic in AWS and Azure to flow between those clouds without transiting campus
Scope
As of , 65 Cornell AWS accounts were configured to use Direct Connect. During this migration, all those AWS accounts will have their existing Direct Connect connectivity updated to use new pathways and AWS resources to connect the Cornell campus network to AWS.
...
Phase | Stage | Timeframe | Status | Activity | Impact on Cornell AWS Account VPC Networks |
---|---|---|---|---|---|
Preparation | Data Collection | November 2022 |
| none | |
Resource Tagging |
|
| none | ||
Resource Groups |
| none | |||
Customer Input #1 | - |
| none | ||
Migration | Transit Gateway Attachments | - |
| none | |
Customer Input #2 | - |
| none | ||
v2 BGP Updated | 7am |
| Azure-to-AWS-VPC traffic may begin to use the v2 architecture (in just the one direction). This is limited only to Azure-to-AWS-VPC traffic due to Cornell's network architecture. | ||
VPC Routing Updated | 9am |
|
| ||
Campus Direct Connect Routes Updated | 9am |
|
| ||
Cleanup | Customer Account Cleanup | - |
| none | |
Campus Direct Connect Cleanup |
| none |
...
- The rollback for the "VPC Routing Updated" step is to reassign the original Route Tables to the public and private subnets. This will rollback takes effect immediately.
- The rollback for the "Campus Direct Connect Routes Updated" step is to the cancel the failover of the Direct Connect Virtual Interfaces that we triggered to initial the campus routing updates. This rollback takes 5-20 minutes to complete.
...
FAQs
How do I tell if my AWS account will be affected by this change?
...
- Cornell Documentation
- Cornell AWS Accounts Affected by 2023 Direct Connect Architecture Migration
- Terraform Configuration Guidance for 2023 Direct Connect Architecture Migration
- Cornell AWS Direct Connect Routing Diagrams
- Announcements
- 2023-01-19 AWS Direct Connect Architecture Migration Completed
- 2023-01-16 AWS Direct Connect Architecture Migration Execution
- 2023-01-10 AWS Direct Connect Architecture Migration Customer Review and Feedback #2
- 2022-12-20 AWS Direct Connect Architecture Design Update
- 2022-12-15 AWS Direct Connect Architecture Migration Customer Review and Feedback
- 2022-12-09 AWS Direct Connect Architecture Migration Preparation Continues
- 2022-11-02 Upcoming AWS Direct Connect Changes
- External Documentation
...