Sort of. If you use private IPs on both side the rate for transfer between availability zones (not regions) is 0.00 per GB. Zero cents. Just another reason not to use public IPs on your ES instances.
David On Friday, August 15, 2014 7:09:52 AM UTC-7, Andrej Rosenheinrich wrote: > > David, you are of course right with 2), but one thing to concider is that > you pay for incoming and outgoing traffic between different availability > zones. > > Am Freitag, 15. August 2014 14:32:54 UTC+2 schrieb David Severski: >> >> Thanks for collecting this information together! A couple points for >> tweaking: >> >> 1) Instead of hard coding the IAM credentials into the file, associate >> the instances with an IAM role. cloud-aws will use those automatically and >> AWS will handle key rotation for you. >> 2) You are launching all the instances into the same availability zone. >> That greatly reduces the ability of the cluster to tolerate an AWS outage. >> Stick each of your three nodes in a different availability zone and you'll >> be much better off. >> 3) EC2-Classic is deprecated. Demonstrating use of VPC would be helpful. >> 4) I encourage AWS hosts _not_ to be named. Users should plan for hosts >> to come and go. This means no-unique host names and hard coded IPs. AWS is >> ephemeral infrastructure and ES, as a cluster app, is very happy playing in >> this space. >> >> and the big one... >> >> 5) Your security group looks to open ES to the world. DON'T DO THIS! >> There's been a tremendous amount of angst recently from ES clusters getting >> owned via open tcp/9200 and these security groups look to open your cluster >> to the entire internet. There's no need for that. cloud-aws will work with >> private IPs just fine. >> >> David >> >> On Thursday, August 14, 2014 10:13:34 AM UTC-7, Pavel P wrote: >>> >>> Hi everyone, >>> >>> Below you can find one big article, summing up all my experience of >>> building the cluster on AWS. >>> When I started I had no information at all, but I found the needed >>> pieces in different places, including this user group. >>> >>> With your help I succeeded, and want to share the knowledge, that >>> newcomers would find everything in one place. >>> >>> Elasticsearch cluster on AWS. Part 1 - preparing the environment. >>> <http://pavelpolyakov.com/2014/08/13/elasticsearch-cluster-on-aws-part-1-preparing-environment/> >>> Elasticsearch cluster on AWS. Part 2 - configuring the elasticsearch. >>> <http://pavelpolyakov.com/2014/08/14/elasticsearch-cluster-on-aws-part-2-configuring-the-elasticsearch/> >>> >>> Hope it would help someone! >>> >>> Regards, >>> >> -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/518c2feb-8c7c-4bef-9a1c-659fea2c1211%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
