Introduction

This document provide information about using a AWS Shared VPC offering once its has been provisioned to your Cornell AWS account.

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 thus 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.

What You'll See

References

• Cornell
  • DRAFT CUSTOMER DOC UPDATE - Shared AWS VPC for Cornell AWS Accounts
  • DRAFT CUSTOMER DOC UPDATE - Shared AWS VPC FAQs
  • Cornell AWS Direct Connect
  • The Cornell Standard VPC
• AWS
  • AWS Resource Access Manager
  • AWS Systems Manager Parameter Store