Merge pull request circleci#3422 from circleci/fix-aws-links

fixing broken links to aws docs

Author: michelle-luna

jekyll/_cci2/aws.md

@@ -92,7 +92,7 @@ Have the following information available before beginning the installation proce
 
 The following additional settings are required to support using private subnets on AWS with CircleCI:
 
-- The private subnet for builder boxes must be configured with a [NAT gateway](https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-nat-gateway.html) or an [internet gateway](https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Internet_Gateway.html) configured for the outbound traffic to the internet via attached route tables. **Note:** The subnet should be large enough to *never* exhaust the addresses.
+- The private subnet for builder boxes must be configured with a [NAT gateway](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html) or an [internet gateway](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Internet_Gateway.html) configured for the outbound traffic to the internet via attached route tables. **Note:** The subnet should be large enough to *never* exhaust the addresses.
 - The [VPC Endpoint for S3](https://aws.amazon.com/blogs/aws/new-vpc-endpoint-for-amazon-s3/) should be enabled. Enabling the VPC endpoint for S3 should significantly improve S3 operations for CircleCI and other nodes within your subnet.
 - Adequately power the NAT instance for heavy network operations.  Depending on the specifics of your deployment, it is possible for NAT instances to become constrained by highly parallel builds using Docker and external network resources.  A NAT that is inadequate could cause slowness in network and cache operations.
 - If you are integrating with [github.com](https://github.com), ensure that your network access control list (ACL) whitelists ports 80 and 443 for GitHub webhooks. When integrating with GitHub, either set up CircleCI in a public subnet, or set up a public load balancer to forward github.com traffic.