Public IP on AWS
Sun, 09/23/2012 - 05:01
Helllo,
I am trying to deploy an AWS backed setup of the community edition server, and I am having trouble creating a cluster since the cloud setup as described here :
http://www.couchbase.com/docs/couchbase-manual-1.8/couchbase-bestpractic...
requires some sort of DNS service and they charge by request so that is an unknown expense that I am trying to avoid as well as the complication of this solution. AWS does have an free Elastic IP service that ties a specific address to a changing IP. but with my limited knowledge of the subject I wasn't able to setup a cluster by myself.
Is it possible to do? if so how?
Thanks,
Yuval
It is possible to do so. Effectively, what you'll want to do is set up the nodes of your cluster and then set up the EIPs to these nodes before you install Couchbase Server. Then, when setting up Couchbase Server you'll configure it as described in the link you pointed out using the EIPs.
Amazon's feature guide on EIPs is here: http://aws.amazon.com/articles/1346
The only thing you need be careful of is that if you replace a server or go to upgrade a cluster, you'll need to remove the EIP from the cluster first.
I will note that EIPs aren't required though. One other approach for your deployment is to edit the configuration as pointed out in http://www.couchbase.com/docs/couchbase-manual-1.8/couchbase-bestpractic... to tie the server to the internal IP. You can use ifconfig or ipconfig to identify the internal IPs on the cluster. The tradeoff for this is the applications accessing it will need to be in EC2 as well. Personally, I prefer this approach as EIPs are really intended for things like loadbalancers. The reason the EIP has been recommended is that it gives you a way to permanently associate a known IP with a running instance.
Do let me know if you have any further questions about this.