With Amazon VPC, you can:

  • Create an Amazon Virtual Private Cloud on AWS's scalable infrastructure, and specify its private IP address range from any range you choose.
  • Expand your VPC by adding secondary IP ranges.
  • Divide your VPC’s private IP address range into one or more public or private subnets to facilitate running applications and services in your VPC.
  • Control inbound and outbound access to and from individual subnets using network access control lists.
  • Store data in Amazon S3 and set permissions such that the data can only be accessed from within your Amazon VPC.
  • Assign multiple IP addresses and attach multiple elastic network interfaces to instances in your VPC.
  • Attach one or more Amazon Elastic IP addresses to any instance in your VPC so it can be reached directly from the Internet.
  • Connect your VPC with other VPCs and access resources in the other VPCs via private IP addresses using VPC Peering.
  • Connect to Amazon S3 without using an internet gateway or NAT, and control what resources, requests, or users are allowed through a VPC endpoint.
  • Bridge your VPC and your onsite IT infrastructure with an encrypted VPN connection, extending your existing security and management policies to your VPC instances as if they were running within your infrastructure.
  • Enable EC2 instances in the EC2-Classic platform to communicate with instances in a VPC using private IP addresses.
  • Associate VPC Security Groups with instances on EC2-Classic.
  • Use VPC Flow Logs to log information about network traffic going in and out of network interfaces in your VPC.
  • Enable both IPv4 and IPv6 in your VPC.

Get Started with AWS for Free

Create a Free Account
Or Sign In to the Console

Receive twelve months of access to the AWS Free Tier and enjoy AWS Basic Support features including, 24x7x365 customer service, support forums, and more.

Please note that Amazon VPC is not currently available on the AWS Free Tier.

AWS resources such as Elastic Load Balancing, Amazon ElastiCache, Amazon RDS, and Amazon Redshift are provisioned with IP addresses within your VPC. Other AWS resources such as Amazon S3 are accessible via your VPC’s Internet Gateway, NAT gateways, VPC Endpoints, or Virtual Private Gateway.

Using the built-in security features of Amazon Web Services like Amazon Identity and Access Management (IAM) policies, VPC Endpoint policies, and Amazon EC2 security groups, you can restrict access to your AWS resources to only accept connections or requests that originate from your VPC. To limit access to your AWS resources like Amazon S3 buckets, Amazon SNS topics and Amazon SQS queues, you can create IAM policies which limit access to those resources to only the Elastic IP addresses associated with your VPC.  You can also use VPC Endpoint policies to control access to Amazon S3 from within your VPC.

 

 

 

Please note the following about Amazon VPC right now:

  • You can have up to five (5) nondefault Amazon VPCs per AWS account per region.*
  • You can have up to four (4) secondary IP ranges per VPC*
  • You can create up to two hundred (200) subnets per Amazon VPC.*
  • You can have up to five (5) Amazon VPC Elastic IP Addresses per AWS account per region.*
  • You can have up to ten (10) Hardware VPN Connections per Amazon VPC.*

* Should you need to exceed these limits, please complete this form. To learn more about VPC limits, please view Amazon VPC Limits in the Amazon Virtual Private Cloud User Guide.

Your use of this service is subject to the Amazon Web Services Customer Agreement.