Release: Amazon EC2 on 2007-10-16

Release Notes>Amazon EC2>Release: Amazon EC2 on 2007 10 16
This release introduces in the instance types feature, which allows you to launch large (m1.large) andextra-large (m1.xlarge) instances in addition to the standard Amazon EC2 instance (now referred to as the small instance).

Details

Submitted By: Attila@AWS
Release Date: October 16, 2007 12:00 AM GMT
Latest Version: 2007-08-29
Latest WSDL: http://ec2.amazonaws.com/doc/2007-08-29/AmazonEC2.wsdl
Created On: October 15, 2007 9:55 PM GMT
Last Updated: October 16, 2007 9:17 AM GMT

New Features

FeatureDescription
New Instance Types
In addition to the standard Amazon EC2 instance, we now provide large (m1.large) and extra-large (m1.xlarge) instances.
For more information, refer to the Amazon EC2 Developer Guide and the New Instance Types Feature Guide.
Instance Launch Time RunInstances and DescribeInstances now return the time when the Amazon EC2 instance launched.
For more information, refer to the Amazon EC2 Developer Guide.

Changes

Feature Description
SSH Key no longer stored on file system
Scripts that require a copy of the public key from the launch key pair must obtain the key from the instance's metadata (not the key file in the ephemeral store) for instances bundled with this AMI tools release and later. AMIs bundled before this release will continue to work normally.
DNS Format
The DNS name format for the new instance types (m1.large and m1.xlarge) is different than that of previous instances. The DNS format has been "ec2-67-202-17-26.z-2.compute-1..." and will be "ec2-67-202-17-26.compute-1..." for the new instance types. Specifically, the token z- is no longer present in the internal and external DNS names.
We will also be adding m1.small instances (the original instance type) with this new DNS format. We anticipate making further changes to our DNS naming and recommend against relying on a specific format of the DNS name. Note that DNS names of running instances will not change.

Known Issues

IssueDescription
Instance type metadata not available in older AMIs.

The instance-type is only available as part of the instance metadata on instances that expose version 2007-09-28 of the instance metadata. Large and extra large instance types support this version. Small instances types (the original instance type) may not support this version yet, in which case the instance type of m1.small can be assumed. You can query supported versions using the following URL: http://169.254.169.254/.

Instance limit New users are limited to a maximum of 20 concurrent instances. If you need a higher limit, contact aws@amazon.com.
Creation of Paid AMIs is limited We are currently accepting only a limited number of partners who will be able to create Paid AMIs. Users interested in selling their Amazon EC2 AMIs through this program should send an e-mail to aws@amazon.com. Please include your name, AWS account ID, company name, and a detailed description of your AMI.
Access to public NAT addresses from within EC2 EC2 instances cannot access instances in the new NAT environment through their public IP addresses; they must access the instances through their private IP addresses. The EC2 DNS servers will return the internal IP address when asked about an instance's public DNS name. In this way, DNS lookups that would resolve to a public EC2 IP address will be translated to the correct internal IP address. This only works when using the EC2 DNS servers from an EC2 instance.
Console output Some instances in the direct-addressing environment report a soft lockup error in the console output during boot. This is a false error that does not impact the successful booting of an instance.
Console output availability There were some reports of full console output not being available. Full console output is only guaranteed for instances that rebooted after this feature was released.
AMIs may launch if its Amazon S3 bundle was deleted. You may be able to launch an AMI after its bundle was altered or deleted from Amazon S3. We discourage deleting an AMI from Amazon S3 without also deregistering the AMI.
ec2-delete-bundle Misleading Error Message The ec2-delete-bundle operation currently returns an error when it attempts to delete an Amazon S3 bucket that is not empty. Despite this error, the files within this bundle are successfully deleted.
©2014, Amazon Web Services, Inc. or its affiliates. All rights reserved.