Hey, Peter --
Thanks for sharing your steps.
The documentation is bare bones... But we'll make it better.
I'd like to give you some more colour:
Elastic App Search is a separate piece of software that relies on Elasticsearch as its data store. It is deployed and managed separately from the underlying Elasticsearch infrastructure. For relatively small installations you can co-locate Elasticsearch and App Search, but for larger deployments we would recommend hosting them separately.
App Search refers to Elasticsearch using a single HTTP(S) endpoint.
You can configure it in
app_search.yml in the
If you have more than one Elasticsearch node - which we'd recommend for production deployment - you need to figure out how you want to distribute traffic across the Elasticsearch cluster. There are multiple options that you could employ that are outside of the scope for this discussion, but the options usually boil down to...
A load balancer in front of the cluster. You can use one or more servers and balance traffic across the cluster since all instances within the cluster are stateless and completely interchangeable.
Using an Elasticserach coordinating node co-located with App Search instances.
For development/testing purposes, you can point App Search at any Elasticsearch node in your cluster and App Search will work as long as that node is alive, and you can just deploy a single instance.
Finally, if you run more than one App Search instance or you deploy it on anything other that localhost, you need to make sure that whatever address you use to reach App Search deployment is set as
Hopefully this helps.
Please let me know what else you discover and whether you have any feedback.