Release: Amazon EC2 on 2010-09-28

Release Notes>Amazon EC2>Release: Amazon EC2 on 2010 09 28
New AWS SDK for PHP.

Details

Submitted By: cheriaws
Release Date: September 28, 2010 12:00 AM GMT
Latest Version: 2010-08-31
Latest WSDL: http://ec2.amazonaws.com/doc/2010-08-31/AmazonEC2.wsdl
Created On: September 28, 2010 3:01 PM GMT
Last Updated: October 21, 2010 5:25 PM GMT

New Features

Feature Description
AWS SDK for PHP AWS now provides a PHP SDK that covers Amazon EC2 and other AWS products. The AWS SDK for PHP provides a library, code samples, and documentation to help developers build PHP scalable web applications. For more information about the AWS SDK for PHP, go to http://aws.amazon.com/sdkforphp.

Known Issues

IssueDescription
Current Limitations for Tags and Filters You currently cannot tag the following resources:
  • Elastic IP addresses
  • Key pairs
  • Security groups
  • 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 Following are current limitations of micro instances:
  • They are not available for use with Amazon Virtual Private Cloud
  • They are not available for use with Amazon Elastic MapReduce
  • They are not available for use with Amazon DevPay
Current Limitations for Cluster Compute Instances Following are current limitations of cluster compute instances:
  • They support Linux/UNIX operating systems, but currently not Microsoft Windows Server
  • They are available only in the US-East (Northern Virginia) Region
  • Spot Instance requests for cluster compute instances are not supported
  • They are not available for use with Amazon Virtual Private Cloud
  • They are not available for use with Amazon DevPay
Current Limitations for Cluster Placement Groups Following are current limitations of cluster placement groups:
  • You can't currently use Auto Scaling to launch cluster compute instances into a cluster placement group
  • Reserved Instances are not currently available within a cluster placement group
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 where setting the TCP_MAXSEG socket option on TCP sockets to certain values (known values include 1500) causes the kernel to generate TCP Segmentation Offload (TSO) packets of invalid size that are then dropped by the NIC driver, resulting in very low network throughput. Don't set this socket option and let the kernel handle segmentation and Path Maximum Transmission Unit (PMTU) discovery using the default settings.
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 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.
©2014, Amazon Web Services, Inc. or its affiliates. All rights reserved.