Recent AWS Customer Success Stories & Videos

More AWS Customer Success Stories...

« The AWS Report - Travis Broughton of Intel - Expressway Service Gateway | Main | The AWS Report - Nihar Bihani Talks about Amazon CloudFront »


Feed You can follow this conversation by subscribing to the comment feed for this post.

Aravind Krishnaswamy

Hey Jeff,

Will this Auto assigned public IP be static? Does it behave the same way as an EIP does?


Jeff Barr

Here is how it works:

• When the instance is stopped, the publicIP is removed, just like Classic. When the instance is started, it gets a new publicIP, just like Classic.

• You can still associate an EIP with an instance with a publicIP, just like Classic. When you disassociate the EIP, a publicIP is assigned again, just like Classic.


Will the outbound connection from an instance in VPC be coming from public ip or private ip. In the past even if we attach an EIP the out bound connection appears to come from private IP. Please clarify.


Still no ipv6 for vpc ELB? Need this asap.

Phil Howard (aka Skaperen)

This feature is degraded in us-west-1 (N. California) because the "Public DNS" field (and its metadata equivalent public_hostname) are providing empty data. Instances can get public_ipv4, but users of the web console interface cannot see the IP address (because the instances page has no column for it) or hostname (because this feature is broken). A workaround is to look at the network interfaces page where a column is available to show the external IP. This problem does not exist in us-east-1 or us-west-2. I have not tried others.

The comments to this entry are closed.

Featured Events

The AWS Report

Brought to You By

Jeff Barr (@jeffbarr):

Jinesh Varia (@jinman):

Email Subscription

Enter your email address:

Delivered by FeedBurner

April 2014

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30