Release: Amazon EC2 on 2011-03-27
New Dedicated Instances option for instances launched into a VPC, and a new API version: 2011-02-28
Release Date: March 27, 2011
Latest Version: 2011-02-28
Created On: March 28, 2011
Last Updated: October 09, 2017
New Features
Feature | Description |
---|---|
New API Version | With this release, Amazon EC2 has a new API version (2011-02-28). The WSDL is at http://ec2.amazonaws.com/doc/2011-02-28/AmazonEC2.wsdl. To get the latest version of the API tools, go to Amazon EC2 API Tools. |
New Amazon EC2 Dedicated Instances | Dedicated Instances are Amazon EC2 instances launched within your Amazon Virtual Private Cloud (Amazon VPC) that run hardware dedicated to a single customer. Dedicated Instances let you take full advantage of the benefits of Amazon VPC and the AWS cloud—on-demand elastic provisioning, pay only for what you use, and a private, isolated virtual network—all while isolating your Amazon EC2 compute instances at the hardware level. |
Known Issues
Issue | Description |
---|---|
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:
|
Instance Clock Drift | Some instances (Windows instances in particular) can experience a system clock drift. The issue appears to be more severe in t1.micro Windows instances that run CPU-intensive workloads. If your application is sensitive to time drift, consider using other instance types until a resolution is available. |
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 AMIs 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 10GB 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 How to Attach 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, but many of our customers use hundreds or thousands of instances. If you need a higher limit, go to http://aws.amazon.com/contact-us/ec2-request. |