Ok..yes..using a EIP worked. Thanks and will now up my understanding of NAT
Thanks On Sat, Jun 22, 2013 at 12:46 PM, Andrew Thompson <and...@hijacked.us>wrote: > By default AWS machines use NAT, they provide a temporary external IP > that is NATed through to the internal IP applied to the AWS instance. > You can also permanantly assign an 'elastic IP address' if you want a > particular instance to always be reachable on a specific IP. > > > http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html > > When you put that public IP in the riak config file, it makes no sense > to Riak because that IP isn't applied to any interface it knows about. > When you put the private IP in, it works, but you can't access it. This > is probably because AWS is dropping inbound traffic by default: > > > http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html#default-security-group > > This is not a Riak problem, it is an issue with configuring AWS. > > Andrew > > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
