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.

« Getting started with deployments What are deployment templates? »
Elastic Docs ›Elastic Cloud Enterprise Reference [2.1] ›Getting started with deployments

Create your deployment

edit

Create your deployment

edit

Deploy Elasticsearch, Kibana and other products or features of the Elastic Stack quickly by picking one of our tried-and-true templates. Templates pre-select initial hardware configurations that you can deploy as-is, or customize further to match your use case. Learn more …​

To get up and running with your deployment quickly:

  1. From the Cloud UI, click Create deployment.
  2. Pick your Elastic Stack version and give your deployment a name.

  1. Optimize your deployment for your use case by selecting a deployment template. To learn more about how optimizing your deployment works, see What Are Deployment Templates?

    Elastic Cloud Enterprise includes the following deployment templates:

    Default
    A template to get you started and for backwards compatibility with existing deployments. The default template is suitable for search and general all-purpose workloads that don’t require more specialized resources. What’s included …​
    Hot - Warm Architecture
    Use for time-series analytics and logging workloads that benefit from automatic index curation. What’s included …​

    To use this template effectively, you must tag your allocators, so that ECE knows where to send hot and warm data.

    After a deployment is spun up, you can scale the size and add other features; however, the instance configuration and computing ratios cannot be changed. If you need to change an existing deployment to another template, we recommend migrating your data.

  2. Enable additional features, such as:

    Machine learning (ML)
    Detect anomalies with data modeling to find trends, periodicity, and more. Learn more …​.
    Application performance monitoring (APM)
    Monitor the performance of your applications in real time. Learn more …​.

  3. Optional: Restore an Elasticsearch snapshot from another deployment.

    Restoring a snapshot can help with major version upgrades by creating a separate, non-production deployment where you can test, for example. Or, make life easier for your developers by providing them with a development environment that is populated with real data.

  4. At this point, you can:

    • Click Create deployment to get started right away. Recommended if you are a trial user or new to the Elastic Stack.
    • Click Customize configuration to tweak the performance of the Elastic Stack by changing the size of your instances, including of your Elasticsearch clusters, for example. You can also change the level of fault tolerance, configure additional features, and much more. Learn more …​
  5. After your deployment is ready, write down the password for the elastic user (or the admin user for version 2.x) and keep it somewhere safe. You need the password to connect to your Elasticsearch cluster and Kibana. (Missed it? Reset the password.)

That’s it! Now that you are up and running, connect to the Elasticsearch cluster in your deployment, add some data, and then start exploring with Kibana, our open-source visualization tool. If you’re not familiar with adding data, yet, Kibana can show you how to index your data into Elasticsearch.

Want to take Kibana for a test ride first? In Kibana 6.4.0 and later, you can use the one-click sample data, which allows you to use Kibana without loading your own data. For more information, refer to Explore Kibana using the Flight dashboard.

« Getting started with deployments What are deployment templates? »