Release: Amazon EC2 on 2013-03-11
This release of Amazon Elastic Compute Cloud (Amazon EC2) introduces support for copying an AMI from one AWS region to another and support for default virtual private clouds (VPC).
Release Date: March 11, 2013
Latest Version: 2013-02-01
Created On: March 11, 2013
Last Updated: October 09, 2017
New Features
Feature | Description |
---|---|
Copying an AMI from one region to another |
You can copy an AMI from one region to another, enabling you to launch consistent instances in more than one AWS region quickly and easily. For more information, see Copying AMIs in the Amazon Elastic Compute Cloud User Guide. |
Launching instances into a default VPC |
Your AWS account is capable of launching instances into either the EC2-Classic or EC2-VPC platform, or only into the EC2-VPC platform, on a region-by-region basis. If you can launch instances only into EC2-VPC, we create a default VPC for you. When you launch an instance, we launch it into your default VPC, unless you create a nondefault VPC and specify it when you launch the instance. For more information, see Supported Platforms in the Amazon Elastic Compute Cloud User Guide. |
Version History
To view earlier Amazon EC2 release notes, see
Current Limitations for VM Import
The following are current limitations of VM Import:
- The following types of images currently cannot be imported into Amazon EC2:
- VMware Workstation VMDK images
- Encrypted, compressed, or read-only images
- Started or suspended images
- Linked clones
- Images with multiple virtual disks
- When you import a disk image to an Amazon EC2 instance, the instance appears
in the AWS Management Console before the conversion process finishes.
To determine when the process is complete and the instance is available
to use, use the
ec2-describe-conversion-tasks
command.
Current Limitations for M3 Standard Instances
The following are current limitations of m3.xlarge and m3.2xlarge instances:
- All M3 standard instance types are only available in the US East (N. Virginia) Region.
Current Limitations for Cluster Instances
The following are current limitations of cluster compute and cluster GPU instances:
- All cluster instance types are available in the US East (N. Virginia) and EU (Ireland) Regions. In addition, the cc2.8xlarge instance type is also available in the US West (Oregon) Region.
- Amazon DevPay is not supported.
Current Limitations for Cluster Placement Groups
The following are current limitations of cluster placement groups:
- Reserved Instances are not currently available within a cluster placement group
Current Limitations for Tags and Filters
You currently cannot tag the following resources:
- Elastic IP addresses
- Key pairs
- Placement groups
You can currently filter your resources in the AWS Management Console by
tag, but not by the other filters that are available to use with Describe*
actions through the command line tools or API.
Current Limitations for Micro Instances
The following are current limitations of micro instances:
- Amazon Virtual Private Cloud is not supported
- Amazon Elastic MapReduce is not supported
- Amazon DevPay is not supported
Setting the TCP_MAXSEG Socket Option
The 2.6.18-164.15.1 kernel used in the CentOS 5.4 reference AMI contains a known issue: Setting the TCP_MAXSEG socket option on TCP sockets to certain values (for example, 1500) causes the kernel to generate TCP Segmentation Offload (TSO) packets with invalid sizes that the NIC driver then drops. The impact is significantly lower network throughput. As a workaround, don't set this socket option and let the kernel use the default settings to handle segmentation and Path Maximum Transmission Unit (PMTU) discovery.
Query Version of ModifyInstanceAttribute
The ModifyInstanceAttribute action currently does not allow you to modify the block device mapping for the instance.
Paid AMIs Backed by Amazon EBS
Amazon EBS-backed AMIs are not currently supported by Amazon DevPay.
Windows AMI Launch Times
Windows AMIs take longer to launch than Linux/UNIX instances due to larger AMI sizes and multiple reboots.
Windows AMI Sizes
Installing software on Amazon S3-backed Windows AMIs can cause them to become large and easily reach the 10 GB limit. Before bundling, check the size of the C:\ volume.
Limitation on Drive Mapping
There are limitations on devices available for storage attachment. For more information, see Attaching the Volume to an Instance in the Amazon Elastic Compute Cloud User Guide.