Hi folks, After trying a couple of configurations, I'd recommend using a VPC on EC2. I decided to share my experience with a wider audience and wrote about it on a blog post <http://deepakbala.me/2013/02/08/deploying-riak-on-ec2/>. The post details (among other things) why VPC can make your life much easier. Thank you again for all your suggestions.
Is there a Riak wiki that I can contribute this information to ? It would be easier for users to choose between deployment solutions if they know what options are available. Thanks -Deepak On Sat, Jan 12, 2013 at 1:02 PM, Deepak Balasubramanyam < [email protected]> wrote: > Thanks for all the suggestions. I will take some time to review and try > them out. I'll get back to this thread when I do. > > -Deepak > > > On Thu, Jan 10, 2013 at 3:04 PM, Richard Shaw <[email protected]> wrote: > >> Hi Matt, >> >> For stopping and starting rather than rebooting, you need to use >> elastic IPs inside of Amazon's virtual private cloud[1] which allows >> for persistent static private addresses. >> >> [1]http://aws.amazon.com/vpc/ >> >> Regards >> >> Richard >> >> On Thu, Jan 10, 2013 at 6:09 AM, Matt Black <[email protected]> >> wrote: >> > A quick update on this subject. >> > >> > Using an Elastic IP won't help with AWS since that only binds to the >> public >> > interface - not the internal private one. The hostname command still >> returns >> > the same internal IP address as before, which is what's seen by Riak. >> > >> > In AWS an internal IP address will actually persist across reboots. It >> does >> > not persist across shutdown and startup. >> > >> > >> >> _______________________________________________ >> riak-users mailing list >> [email protected] >> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >> > >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
