| Issue | Description |
|---|
| VPC Resource Limitations |
VPC resources are limited. For more information, go to Amazon VPC Limits
in the Amazon Virtual Private Cloud User Guide. |
| CC1 instances |
CC1 instances are not supported for use in a VPC. |
| VPC Dashboard filtered view |
If you have created more than one VPC and choose to filter the
VPC dashboard view to only view a single VPC, the resource counts for
security groups, Internet gateways, virtual private gateways, customer
gateways, and VPN connections reflect all VPCs. |
| Older API Version Clients and Latest Console Display Different Results |
If you use a client that is based on an older API
version of Amazon VPC (earlier than version 2011-01-01), but you also
use the AWS Management Console to manage your VPC resources, you'll see
different results between the two interfaces. |
| Elastic IP Addresses Not Interchangeable |
Any EC2 Elastic IP addresses your AWS account has
cannot be used with your VPC, and any VPC Elastic IP addresses you have
can't be used with EC2. |
| Security Groups Not Interchangeable |
Any EC2 security groups your AWS account has
cannot be used with your VPC, and any VPC security groups you have can't
be used with EC2. |
| Traffic Sent to Overlapping IP Address Ranges Is Dropped |
For customers using the optional IPsec VPN
gateway: If your VPC's IP address range overlaps with an IP address
range in use within your existing IT infrastructure, Amazon VPC will
drop any traffic to said range. To avoid this, create your VPC so it
does not overlap with current or expected future subnets in your
network. |
| Broadcast and Multicast Unsupported in a VPC |
You are unable to employ either broadcast or multicast within your VPC. |
| Ordering of DHCP Option Values Not Guaranteed |
When you specify DHCP options, some options
(e.g., DNS servers) accept multiple values. The ordering of these values
is not guaranteed. After creating the options, you should use the
DescribeDhcpOptions operation (or the ec2-describe-dhcp-options command)
to confirm the order in which the options will be delivered to
instances. |
| Tags for Amazon VPC Resources Not Supported in the Console |
You can tag your Amazon VPC resources using the
API or command line tools, but those tags are not available to work with
in the AWS Management Console.
|
Release: Amazon Virtual Private Cloud on 2012-10-18
