...
- Deployment of resources that don't need access to the private Cornell network
- Deploying a public web site or API. (Public subnets would be required to deploy a publicly accessible web site, but the initial release of the Shared VPC offers only private subnets.)
- 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 large 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)
...