Release: Amazon EC2 on 2007-02-08

Release Notes>Amazon EC2>Release: Amazon EC2 on 2007 02 08
This release introduces features to programmatically capture console output and reboot instances.

Details

Submitted By: Attila@AWS
Created On: January 24, 2007 11:20 AM GMT
Last Updated: February 28, 2007 3:12 PM GMT

Release Date: 2007-02-08
Latest WSDL/API Version: 2007-01-03

New Features

FeatureDescription
Console Output This release introduces a new API to programmatically capture console output. Matching command line tools are also included. For more details, see the Developer Guide and the article on capturing console output and rebooting instances.
Reboot Instances This release introduces a new API to programmatically reboot instances. Matching command line tools are also included. For more details, see the Developer Guide and the article on capturing console output and rebooting instances.

Resolved Issues

IssueDescription
Long launch times Previously, under certain conditions such as very large launches, instances were taking longer than intended to move into the running state. We made several improvements in this area.

Known Issues

IssueDescription
Instance limit New users are currently limited to a maximum of 20 concurrent running instances. Contact aws@amazon.com if you need a higher limit.
Console output Some instances report a spurious error about soft lockup during boot in their console output. This doesn't impact the successful boot of an instance. Since this has no impact, we are gradually rolling a patch.
Console output availability Full console output is only guaranteed to be available for instances that rebooted after this feature was made available.
AMIs may launch if their bundle in S3 was deleted. Currently it may be possible to launch an AMI even after its corresponding bundle was altered in, or deleted from, S3. We discourage deleting an AMI's bundle out of S3 without also deregistering the AMI.
Deregistered AMIs Describing images currently returns deregistered AMIs for an undefined period after deregistration.
ec2-delete-bundle tool The ec2-delete-bundle tool currently returns an error when it attempts to delete a non-empty bucket in S3. Despite this error, the files making up the bundle are successfully deleted. The error is misleading.
Instances stuck "shutting-down" On occasion, instances may remain in the shutting-down state for longer than expected. Instances will not get charged when they are in this state.
©2014, Amazon Web Services, Inc. or its affiliates. All rights reserved.