This section applies to you if you want to install Elastic Cloud Enterprise by directly downloading it from Elastic. A typical installation requires internet access.
You start setting up a new Elastic Cloud Enterprise installation by installing the software on your first host. This first host becomes the initial coordinator and provides access to the Cloud UI, where you can manage your installation.
To install Elastic Cloud Enterprise on your first host:
Download and run the installation script:
bash <(curl -fsSL https://download.elastic.co/cloud/elastic-cloud-enterprise-installer.sh)
Installation can take a while to complete as it downloads the Elastic Cloud Enterprise image.
During installation, the secrets used by the system for security are generated, as well as root certificates to generate intermediate and client certificates to encrypt SSL communication among all of the services. The root password and the generated certificates are located in ``/mnt/data/elastic/bootstrap-state/bootstrap-secrets.json`, unless you passed in a different path with the
Keep this information secure.
Copy down the URL and user credentials for the administration console provided to you at the end of the installation process. You will use this information to log into the Cloud UI later on. For example:
Administration Console Details: URL: http://192.168.50.10:12400 (See documentation for HTTPS details) Username: root Password: fTao-oa3x8SxT4GjKOlsF6Xy7Ez5C2EvJIW64DrbdT4=
If you plan to install Elastic Cloud Enterprise on additional hosts, copy down the details for the
--coordinator-host HOST_IPparameter, where
HOST_IPis the IP address of the host you just installed on. For example:
To add hosts to this Elastic Cloud Enterprise installation, include the following parameter when you install the software on additional hosts: --coordinator-host 192.168.50.10
- Log into Cloud UI to provision your cluster or follow the steps in the next section to add more hosts first.
A note on output shown during the installation process
The script writes bootstrap status information to standard output. Unless you see stack traces, this status information is an expected part of the process.
There might be some errors shown during the installation that can be ignored safely, such as:
Error deleting container: Error response from daemon: Cannot destroy container bfe798eaf9d2525de16366ffb02d335252bbe532d5eb6a7776cdb73944fd9845: Driver aufs failed to remove root filesystem bfe798eaf9d2525de16366ffb02d335252bbe532d5eb6a7776cdb73944fd9845: rename /mnt/data/docker/aufs/mnt/bfe798eaf9d2525de16366ffb02d335252bbe532d5eb6a7776cdb73944fd9845 /mnt/data/docker/aufs/mnt/bfe798eaf9d2525de16366ffb02d335252bbe532d5eb6a7776cdb73944fd9845-removing: device or resource busy
Error response from daemon: Unable to remove filesystem for 3279e8fe8091820d4aa5b518c2488e2fe481b7dedff91515079ef0ce34edfc70: remove /mnt/data/docker/containers/3279e8fe8091820d4aa5b518c2488e2fe481b7dedff91515079ef0ce34edfc70/shm: device or resource busy
You install Elastic Cloud Enterprise on additional hosts to add them as resources to an existing installation.
For example, if you need more processing capacity for Elasticsearch nodes in your cluster, you can add a host by installing Elastic Cloud Enterprise on it and then assign the allocator role in the Cloud UI. Or maybe you to want to create a cluster that is fault-tolerant and can be used for production? You’ll need to make sure there are enough resources available to support multiple availability zones.
To install Elastic Cloud Enterprise on additional hosts:
Download and run the installation script on each additional host. Include the
--coordinator-host HOST_IPparameter provided to you when you installed on the first host, where
HOST_IPis the IP address of the first host. For example,
bash <(curl -fsSL https://download.elastic.co/cloud/elastic-cloud-enterprise-installer.sh) --coordinator-host HOST_IP
If you are creating a larger Elastic Cloud Enterprise installation that needs to be fault tolerant or highly available, include the
--availability-zone ZONE_NAMEparameter to specify the name of an availability zone for the additional host, which determines which failure domain the host should belong to. Hosts should go into three different availability zones for production systems. For example, invoking the installation script with
bash elastic-cloud-enterprise-installer.sh --coordinator-host 192.168.50.10 --availability-zone ece-region-1cadds the new host to an existing Elastic Cloud Enterprise installation where the first host has the IP address
192.168.50.10and places the additional host into availability zone
After installation completes, additional hosts come online as runners with some roles assigned to them. You can assign new roles to nodes to define the topology of clusters in the Cloud UI later.
For automation purposes, you can set up a DNS hostname for the coordinator host. Setting up a round robin CNAME should be enough to ensure that the value does not need to change in automation scripts. Any one coordinator can be used, including the initial coordinator (the first host you installed Elastic Cloud Enterprise on).