Page History

...

The initial deployment of the Shared VPC will supply only private subnets to opted-in Cornell AWS accounts. This means that the Shared VPC cannot be used to host a public web site or public APIs, for example. Please contact Paul Allen with feedback about access to public subnets in the Shared VPC.

Benefits of Using the Shared VPC

...

• Deployment of resources that don't need access to the Cornell network
• Deploying a public web site or API (Public subnets would be required, but which the Shared VPC does not provide)
• Cornell private network access in regions other than us-east-1 (N. Virginia)
• Need to directly customize Network ACLs, Route Tables, or other VPC configuration
• Peering to non-Cornell VPCs
• Ability to use a vast number of private Cornell IP addresses in AWS
• Deploying Kubernetes or using EKS (Kubernetes consumes vast numbers of IP addresses, which is incompatible with the Shared VPC model)

...