Playbook for productionedit

To get started, you can use one of the 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.

Choose the deployment scenario that best fits your business need. You can also scale your deployment from one example to another, up or down. While migrating from one installation type to another, make sure to:

  • Back up the information in the bootstrap-secrets.json file, by removing it from its default location and placing it into a secure storage location.
  • Migrate proxies from original control plane hosts to new hosts, before starting the migration of director and coordinator.

Before you beginedit

Before 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.