| Issue | Description |
| 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 S3 bundle was deleted. | You may be able to launch an AMI after its bundle was altered or deleted from S3. We discourage deleting an AMI from 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 S3 bucket that is not empty. Despite this error, the files within this bundle are successfully deleted. |
