Page History

...

• Customers cannot use the Shared VPC to deploy systems that utilize large quantities of IPv4 addresses. For example:
  • Kubernetes clusters and the Amazon Elastic Kubernetes Service (EKS) both use large numbers of IP addresses, even for trivial deployments, and so should not be deployed to the Shared VPC.
  • Large AWS EMR deployments. EMR clusters with a handful of nodes are OK.
• If you configure a deployment that does consume vast quantities of IP addresses in the shared VPC and is negatively affecting other Shared VPC customers, the resources created by the deployment may be, in an urgent situation, destroyed in order to remove or reduce the impact to other Shared VPC customers.
• We cannot customize the Network ACL used by the Shared VPC for arbitrary customer needs. However, since the Shared VPC is a new offering, there may be adjustments needed to accommodate reasonable use-cases we had not envisioned. Please contact Cloud Support to discuss.
• We cannot peer the Shared VPC with arbitrary AWS VPCs, whether or not those VPCs are owned by Cornell AWS accounts. All Cornell VPCs on the private Cornell network are already accessible to the Shared VPC via the Direct Connect Transit Gateway architecture.
  
  • If you have a use case where massive quantities of data are being passed between the Shared VPC and a Cornell Standard VPC, contact Cloud Support to discuss whether a direct peering would be beneficial for cost or latency efficiencies.

...