...
- 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.
- Large AWS EMR deployments. ( EMR clusters with a handful of nodes are OK.).
- 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 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.
TBD
Best Practices
- Use Security Groups applied to resources deployed in the Shared VPC to restrict ingress to those resources, even by traffic from the local VPC and subnets. You don't want to be affected by something dumb another team does when they are using the Shared VPC.
- When deploying replicas of a specific resource, be sure to spread them out across multiple subnets and multiple AZs.
- Be especially careful about configuring resources that automatically scale up (e.g., EC2 Auto Scaling Groups).
- If you are managing Elastic Network Interfaces directly, be sure to delete them once they are no longer needed.
...