Release: Amazon EC2 on 2007-03-22

Release Notes>Amazon EC2>Release: Amazon EC2 on 2007 03 22
This release introduces the Network Address Translation (NAT) addressed instances.


Submitted By: Attila@AWS
Created On: February 28, 2007 4:04 PM GMT
Last Updated: March 23, 2007 5:26 AM GMT

Release Date: 2007-03-22
Latest WSDL/API Version: 2007-01-19

New Features

NAT Addressed Instances
Amazon EC2 is migrating from its current direct addressed instances to NAT addressed instances.  This release introduces a new API and tools to allow users to launch NAT-addressed instances.

NAT adressed instances are allocated two IP addresses: 1) a non-routable private (RFC1918) IP address on the instance, and 2) a public IP address.  A NAT translation maps traffic between these addresses.  These instances will also be provided with both a public and private DNS name.

For more details, see the Technical Documentation and the article about Migrating from Direct Addressing to NAT Addressing.

Known Issues

Instance limit New users are currently limited to a maximum of 20 concurrent running instances. Contact if you need a higher limit.
Access to public NAT addresses from within EC2 EC2 instances cannot access instances in the new NAT environment using their public NAT IP address. Instead, their private address must be used.
The EC2 network will alter DNS responses from external DNS servers by replacing the public IP address for any EC2 instance in the new NAT environment with its private IP address. 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 UDP DNS protocol.
Console output Some instances in the direct-addressing environment report a spurious error about soft lockup during boot in their console output. This doesn't impact the successful boot of an instance.
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.
©2017, Amazon Web Services, Inc. or its affiliates. All rights reserved.