Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Excerpt

This document provides practical information about using either the Multitenant Subnets or Exclusive Use Subnets Shared VPC offering once its has been provisioned to your Cornell AWS account.

Anchor
best-practices
best-practices
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.
  • Don't change the tags that "come with" the shared resources. But, feel free to add additional tags as you see fit. See Tagging below for more information.

...