Accessing ES deployed at EC2 via Transport Client


(Jan Fiedler) #1

I deployed 2 ES instances at Amazon EC2 with the cloud-aws plugin
installed and configured. The two nodes form a cluster as expected.

I now try to access the cluster from my local development machine via
the transport client (using the public DNS name of the EC2 instance).
I also opened TCP port 9300 in the Amazon security group for this to
work. When trying to access something like cluster status via the
transport client I always get exceptions (on the client side)
indicating that no node is available.

Is there something conceptually wrong in this setup? Should it be
possible to access an ES node running at EC2 remotely ?


(Shay Banon) #2

I think that what happens is that the nodes formed on the transport client side use the private ip addresses and not the public ip address of the machines. This is what you want when you are within amazon, but not what you want when you go outside it.

Can you open an issue for this? I will think of a way to solve this...

-shay.banon
On Friday, December 10, 2010 at 4:34 PM, Jan Fiedler wrote:

I deployed 2 ES instances at Amazon EC2 with the cloud-aws plugin
installed and configured. The two nodes form a cluster as expected.

I now try to access the cluster from my local development machine via
the transport client (using the public DNS name of the EC2 instance).
I also opened TCP port 9300 in the Amazon security group for this to
work. When trying to access something like cluster status via the
transport client I always get exceptions (on the client side)
indicating that no node is available.

Is there something conceptually wrong in this setup? Should it be
possible to access an ES node running at EC2 remotely ?


(system) #3