It is time to say goodbye: This version of Elastic Cloud Enterprise has reached end-of-life (EOL) and is no longer supported.
The documentation for this version is no longer being maintained. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Playbook for production
editPlaybook for production
editTo make getting started easier, we have come up with three tested Elastic Cloud Enterprise deployment scenarios that are all suitable for production systems:
When running the deployment commands, you must define the memory configurations for each role: "zookeeper":{"xms":"4G","xmx":"4G"}. Otherwise, the default settings will be used.
Which deployment scenario you pick depends on your business need, but you can scale your installation from one example to another, up or down.
Before you begin
editBefore you can deploy Elastic Cloud Enterprise, you need to:
- Plan Your Deployment. Use our guidance to help you decide how you should install Elastic Cloud Enterprise, including information on recommended hardware, high availability for production systems, the use of a load-balancer, and more.
- Check the prerequisites. Make sure you meet the requirements for software, hardware, users, networking, and JVM heap sizes. Pay special attention to what Linux kernel and Docker versions you plan to use and follow our recommendations. Our testing has shown that not all software combinations work well together.
- Prepare your environment. You can install Elastic Cloud Enterprise on your own hardware or on many cloud environments, such as AWS or GCP, but you need to get your hosts ready for installation before you can run through the rest of this playbook.