You will get a public address to connect on.
You have only to open some ports (9300 and if needed 9200).
Twitter : @dadoonet / @elasticsearchfr
Le 12 juin 2012 à 07:01, Dennis firstname.lastname@example.org a écrit :
Had another brainstorm, probably known by the more experienced ones on this list.
Cloudbees is on EC2. If I start an EC2 instance of ElasticSearch, I will get a private IP address. Will I be able to connect to it on port:ESPort#/ ?
For now I'm using http transport in Java, but I'll write using the Java API soon. I guess I just need a unique server name on my ES instance?
On Monday, June 11, 2012 8:21:32 PM UTC-7, Dennis wrote:
A good, temporary substitute, since I'm using java HttpClient to the localhost to get around some problems would be accessing a remote instance via public IP.
I've looked and I must not be seeing it, if it's available.
I only need a single machine instance right now.
On Monday, June 11, 2012 7:45:24 PM UTC-7, Dennis wrote:
CloudBees is a nice little site. the preset up Jenkins and java environment is great for dev and small deploys.
However, their choice of popular applications does not include ElasticSearch. I have looked through all of the possibilties, and it still comes up short. ES is the easiest of all search engines to use, has the features I want out of the box, and is perfect as document/entity store.
Soooo, anyone heard of a way to deploy it on Cloudbees?
Shay, you interested in jumping on CloudBees ramp up to success? They should end up being a decent, mid market, major share holder for Java developers.