*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
...
| Gliffy Diagram | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Features
Features Available at Initial Release
- One private subnet in each Availability Zoneof the sic Availability Zones available in us-east-1.
- One NAT Gateway in each Availability Zone. Each private subnet routes internet-bound traffic to the NAT Gateway in the same Available Zone, providing maximal resiliency.
- Direct Connect connectivity to private and public campus networks, and to private Cornell VNets in Azure
- Connectivity to all Cornell Standard VPCs in AWS, without leaving the us-east-1 AWS Region.
- Gateway endpoints for S3 and Dynamo DB reside in the VPC making VPC communication with those services quick and private.
- If you have need for other AWS service endpoints deployed to the Shared VPC, please contact Cloud Support.
- A slightly modified version of the Baseline AWS Network ACL is applied to all private subnets. (The single change is that the inbound rule allowing traffic to port 22 from the internet is removed. ( Inbound traffic on port 22 is still allowed from Cornell private and public networks.)
...
- Manual deployment of a few resources that require access to the Cornell private network
- Deployment of three-tier (or more!) applications in the Shared VPC
- Using Infrastructure as Code to create and manage AWS resources in the Shared VPC
- Standing up an RDS instance in the private Cornell network
- Deploying an API Gateway API or Lambda function with access to the Cornell network
- Deployment of resources which will be accessed only by users on the Cornell VPN
Misuse Cases
Misuse cases are situations where the Shared VPC should not or cannot be used. Some of those are:
...