Release: Amazon EC2 on 2012-09-11
New Features
| Feature | Description |
|---|---|
| Amazon EC2 Reserved Instance Marketplace |
The Reserved Instance Marketplace now provides AWS customers the flexibility to sell their Amazon Elastic Compute Cloud (Amazon EC2) Reserved Instances to other businesses and organizations. Customers can browse the Reserved Instance Marketplace to find an even wider selection of Reserved Instance term lengths and pricing options sold by other AWS customers. As your needs change, the Reserved Instance Marketplace gives you the flexibility to sell the remainder of your existing Reserved Instances at the price you select. After a buyer purchases your Reserved Instance and AWS receives payment, funds will be deposited via ACH wire transfer into your bank account and you will receive an email notification. You can also now shop the Reserved Instance Marketplace to purchase Reserved Instances outside the standard one-year and three-year term lengths. Amazon EC2 Instances purchased on the Reserved Instance Marketplace offer the same capacity reservations as Reserved Instances purchased directly from AWS. For more information, see Reserved Instance Marketplace. |
Version History
To view earlier EC2 Release Notes please see http://aws.amazon.com/releasenotes/Amazon EC2.
Known Issues
| Current Limitations for VM Import |
Following are current limitations of VM Import:
|
| Current Limitations for Cluster Instances | Following are current limitations of cluster compute and cluster GPU instances:
|
| Current Limitations for Cluster Placement Groups | Following are current limitations of cluster placement groups:
|
| Current Limitations for Tags and Filters | You currently cannot tag the following resources:
Describe* actions through the command line tools or API. |
| Current Limitations for Micro Instances | Following are current limitations of micro instances:
|
| Setting the TCP_MAXSEG Socket Option | The 2.6.18-164.15.1 kernel used in the CentOS 5.4 reference AMI (ami-7ea24a17) contains a known issue: Setting the TCP_MAXSEG socket option on TCP sockets to certain values (e.g., 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, go to Attaching the Volume to an Instance in the Amazon Elastic Compute Cloud User Guide. |
| Instance Limit | New AWS accounts are limited to a maximum of 20 concurrent instances (of which 2 may be CG1 instances), but many of our customers use hundreds or thousands of instances. If you need a higher limit, go to Request to Increase Amazon EC2 Instance Limit (http://aws.amazon.com/contact-us/ec2-request). |
