@Yang: Sounds legit, as internal is not the same as external. Beware of the fact that internal traffic is only free when it's in the same availability zone. In the same region is charged with a small amount (~ $0.01).

With kind regards,

Robin Verlangen
Software engineer

W http://www.robinverlangen.nl
E robin@us2.nl

Disclaimer: The information contained in this message and attachments is intended solely for the attention and use of the named addressee and may be confidential. If you are not the intended recipient, you are reminded that the information remains the property of the sender. You must not use, disclose, distribute, copy, print or rely on this e-mail. If you have received this message in error, please contact the sender immediately and irrevocably delete this message and any copies.

2012/9/5 Yang <teddyyyy123@gmail.com>
thanks, but if the communication between cluster nodes all resolve to "internal to internal", amazon will not charge the traffic as external traffic, right?

On Tue, Sep 4, 2012 at 7:08 PM, aaron morton <aaron@thelastpickle.com> wrote:
See http://aws.amazon.com/articles/1145?_encoding=UTF8&jiveRedirect=1#12

The external  dns will resolve to the internal IP when resolved internally.

Using the internal IP means you are not charged for IO and it makes it clear you do not expect this service to be access from outside.


Aaron Morton
Freelance Developer

On 5/09/2012, at 7:37 AM, Yang <teddyyyy123@gmail.com> wrote:

> http://www.datastax.com/docs/1.1/initialize/cluster_init
> says:
> " Note  In the - seeds list property, include the internal IP addresses of each seed node."
> why do I have to use internal IP?
> on a EC2 node,
> hostname resolution seems to directly give its internal IP:
> $ host aws1devbic1.biqa.ctgrd.com
> aws1devbic1.biqa.ctgrd.com is an alias for ec2-50-17-3-229.compute-1.amazonaws.com.
> ec2-50-17-3-229.compute-1.amazonaws.com has address
> so using the public DNS or internal IP seems to be the same thing, or something I'm missing ?
> Thanks
> Yang