Amazon Virtual Private Cloud
User Guide

Document History

The following table describes the important changes in each release of this Amazon VPC guide.

Feature API Version Description Release Date
VPN metrics 2016-11-15 You can view CloudWatch metrics for your VPN connections. For more information, see Monitoring Your VPN Connection. 15 May 2017
IPv6 support 2016-11-15 You can associate an IPv6 CIDR block with your VPC and assign IPv6 addresses to resources in your VPC. For more information, see IP Addressing in Your VPC. 1 December 2016
DNS resolution support for non-RFC 1918 IP address ranges The Amazon DNS server can now resolve private DNS hostnames to private IP addresses for all address spaces. For more information, see Using DNS with Your VPC. 24 October 2016
DNS resolution support for VPC peering 2016-04-01 You can enable a local VPC to resolve public DNS hostnames to private IP addresses when queried from instances in the peer VPC. For more information, see Modifying Your VPC Peering Connection in the Amazon VPC Peering Guide. 28 July 2016
Stale security group rules 2015-10-01 You can identify if your security group is being referenced in the rules of a security group in a peer VPC, and you can identify stale security group rules. For more information, see Working With Stale Security Groups in the Amazon VPC Peering Guide. 12 May 2016
Using ClassicLink over a VPC peering connection 2015-10-01 You can modify your VPC peering connection to enable local linked EC2-Classic instances to communicate with instances in a peer VPC, or vice versa. For more information, see Configurations With ClassicLink in the Amazon VPC Peering Guide. 26 April 2016
NAT gateways 2015-10-01 You can create a NAT gateway in a public subnet and enable instances in a private subnet to initiate outbound traffic to the Internet or other AWS services. For more information, see NAT Gateways. 17 December 2015
VPC flow logs 2015-04-15 You can create a flow log to capture information about the IP traffic going to and from network interfaces in your VPC. For more information, see VPC Flow Logs. 10 June 2015
VPC endpoints 2015-03-01 An endpoint enables you to create a private connection between your VPC and another AWS service without requiring access over the Internet, through a VPN connection, through a NAT instance, or through AWS Direct Connect. For more information, see VPC Endpoints. 11 May 2015



ClassicLink allows you to link your EC2-Classic instance to a VPC in your account. You can associate VPC security groups with the EC2-Classic instance, enabling communication between your EC2-Classic instance and instances in your VPC using private IP addresses. For more information, see ClassicLink.

7 January 2015

Use private hosted zones


You can access resources in your VPC using custom DNS domain names that you define in a private hosted zone in Amazon Route 53. For more information, see Using Private Hosted Zones.

5 November 2014

Modify a subnet's public IP addressing attribute


You can modify the public IP addressing attribute of your subnet to indicate whether instances launched into that subnet should receive a public IP address. For more information, see Modifying the Public IPv4 Addressing Attribute for Your Subnet.

21 June 2014

VPC peering


You can create a VPC peering connection between two VPCs, which allows instances in either VPC to communicate with each other using private IP addresses - as if they are within the same VPC. For more information, see VPC Peering.

24 March 2014

New EC2 launch wizard


Added information about the redesigned EC2 launch wizard. For more information, see Step 3: Launch an Instance into Your VPC.

10 October 2013

Assigning a public IP address


Added information about a new public IP addressing feature for instances launched in a VPC. For more information, see Assigning a Public IPv4 Address During Instance Launch.

20 August 2013

Enabling DNS hostnames and disabling DNS resolution


By default, DNS resolution is enabled. You can now disable DNS resolution using the Amazon VPC console, the Amazon EC2 command line interface, or the Amazon EC2 API actions.

By default, DNS hostnames are disabled for nondefault VPCs. You can now enable DNS hostnames using the Amazon VPC console, the Amazon EC2 command line interface, or the Amazon EC2 API actions.

For more information, see Using DNS with Your VPC.

11 March 2013

VPN connections using static routing configuration


You can create IPsec VPN connections to Amazon VPC using static routing configurations. Previously, VPN connections required the use of the Border Gateway Protocol (BGP). We now support both types of connections and are excited to announce that you can now establish connectivity from devices that do not support BGP, including Cisco ASA and Microsoft Windows Server 2008 R2.

13 September 2012

Automatic route propagation


You can now configure automatic propagation of routes from your VPN and Direct Connect links to your VPC routing tables. This feature simplifies the effort to create and maintain connectivity to Amazon VPC.

13 September 2012

AWS VPN CloudHub and redundant VPN connections

You can securely communicate from one site to another with or without a VPC. You can use redundant VPN connections to provide a fault-tolerant connection to your VPC.

29 September 2011

VPC Everywhere


Support in five AWS regions, VPCs in multiple Availability Zones, multiple VPCs per AWS account, multiple VPN connections per VPC, Microsoft Windows Server 2008 R2 and Microsoft SQL Server Reserved Instances.

03 August 2011

Dedicated Instances


Dedicated Instances are Amazon EC2 instances launched within your VPC that run hardware dedicated to a single customer. Dedicated Instances let you take full advantage of the benefits of Amazon VPC and AWS elastic provisioning, pay only for what you use, and a private, isolated virtual network—all while isolating your instances at the hardware level.

27 March 2011