Release: Amazon EC2 on 2008-08-20

Release Notes>Amazon EC2>Release: Amazon EC2 on 2008 08 20
This release introduces Amazon Elastic Block Store (Amazon EBS).


Submitted By: Bruce@AWS
Release Date: August 20, 2008 12:00 AM GMT
Latest Version: 2008-05-05
Latest WSDL:
Created On: August 21, 2008 3:02 AM GMT
Last Updated: August 22, 2008 4:28 PM GMT

New Features

Amazon Elastic Block Store

Amazon Elastic Block Store (EBS) enables a single Amazon EC2 instance to attach to one or more highly available, highly reliable storage volumes of up to 1 TB of data each.  Once attached, applications on a single Amazon EC2 instance can read or write from the Amazon EBS volume similar to a disk drive.  With Amazon EBS, an Amazon EC2 instance can now be terminated without losing the data that resides on the Amazon EBS volume.  One use case involves running a relational database within an Amazon EC2 instance, but maintaining the data within an Amazon EBS volume.

For more information, refer to the Amazon Elastic Compute Cloud Developer Guide.

Amazon Elastic Block Store Volume Snapshots

Amazon Elastic Block Store (EBS) provides the ability to take point-in-time snapshots of your data, which are then stored in Amazon S3 for long term durability. Snapshots can also be used to create new Amazon EBS volumes from an existing data set or to restore a volume to an older version. Snapshots are point-in-time consistent and incremental to minimize Amazon S3 costs. This means that a snapshot will only contain the data in your volume that has changed since your last snapshot. Previous snapshots of your volume will continue to be available until they are deleted.

For more information, refer to the Amazon Elastic Compute Cloud Developer Guide.


Known Issues

EBS Volume Limit

There is a 20 volume per account limit during the beta. If you need more than 20 volumes, go to

Limitation on Drive Mapping There is currently no support for volume attachment to devices beyond /dev/sdp.
Limitation of AuthorizeSecurityGroupIngress AuthorizeSecurityGroupIngress does not allow port ranges for group grants when using the command-line tools or the Query API. This is only supported through the SOAP API.
Elastic IP Addresses and Existing Connections

After a remap of an Elastic IP to an instance, some preexisting communications (to the old and now unmapped IP address) might continue to work for some time. Because of the behavior of some network devices, existing communications (defined as established source IP, destination IP, port combinations) might continue to use preexisting mappings until the devices refresh their caches. These connections are not reliable after the remap. You should reestablish all communications after you remap. We are working to purge these caches much more quickly.

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:

Instance limit New users 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
Creation of Paid AMIs is limited We are currently accepting a limited number of partners to create Paid AMIs. Users interested in selling their Amazon EC2 AMIs through this program should send an e-mail to Please include your name, AWS account ID, company name, and a detailed description of your AMI.
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.
©2017, Amazon Web Services, Inc. or its affiliates. All rights reserved.