Getting Started

Sign Up for a Trial and Get Hosted Elasticsearch!

This tutorial will walk you though how to sign up for a trial and get started using Elastic Cloud.

What is Included in the Trial?

The 14-day free trial includes a cluster with up to 4 GB memory, 96 GB storage, and high availability (HA) across two zones.

How many documents? As many as you can fit in that node. This will of course be dependent on document size and what kind of queries you execute. You may also choose any of the official plugins that are listed in the Elastic Cloud Console.

We also provide access to several Elasticsearch dashboards that are hosted directly on Elastic Search, including Kibana.

Should you want to upload scripts, we ask that you either register a credit card on the Elastic Cloud console or visit the support page for help. This is simply because we don’t want to run your code without knowing who you are. More background on this choice is available in this article.

How to Sign Up

The signup process is really simple and straightforward. All that is required is an email address. A credit card is optional for the trial and may be added at any time later.

  1. Got to our Elastic Cloud Trial page.
  2. Fill in your email address and click Start Free Trial after taking a peek at the legal terms.
  3. Go and check your mailbox and click on the link in the email. If you haven’t received the email within a few minutes then remember to check your spam folder.

You will be asked to set a password for your account. Once this is done you will be signed in to the Elastic Cloud Console.

Create Your First Cluster

  1. Log into the Elastic Cloud Console, if you aren’t logged in already.
  2. Select Clusters at the top and then click New Cluster. You can now start to configure your cluster:

    Start creating your first cluster on Elastic Cloud
  3. Set the cluster size. During the free trial period, you get access to provision one cluster with 1GB memory, and 24GB storage.
  4. Choose a cloud platform and a region close to you. Elastic Cloud supports:

    • Amazon Web Services (AWS)
    • Google Cloud Plaform (GCP)


      The platform and region cannot be changed after the cluster has been created, so pick the one that you think works best for you. For a region, you can often pick the one that is closest to you.

  5. Select level of fault tolerance. The trial includes high availability (HA) across two zones, that is, across 2 data centers.
  6. Select the Elasticsearch version. The default version is the latest, stable version. You can always upgrade versions, but you will not be able to downgrade once your cluster is up and running.
  7. Select how you want to enable scripting. We strongly recommend not to enable all inline scripts (leave Enable all inline scripts disabled). The defaults for the different supported script types are generally safe to accept as is, unless you have a specific requirement.
  8. For versions before 5.0, select the number of shards. The default is 1. We recommend that you read Sizing Elasticsearch before your change the number of shards.
  9. Choose whether you want to enable or disable automatic index creation.
  10. Choose to either require explicit name for deletions or allow wildcards.
  11. Optional: Select from the list of available plugins.
  12. Optional: Specify any whitelisted user settings that should be added to elasticsearch.yml.
  13. Optional: If you have are on a paid subscription and already have other clusters, you can restore a snapshot from another cluster to your new cluster.
  14. Optional: Name your cluster.
  15. Click on the Create Cluster button. Your cluster will be up and running shortly.

    If you created your first cluster on Elasticsearch 5.0 or later, the X-Pack security features are always enabled and a window will pop up with the password for the elastic user. Make sure you copy down this password, as you will need it when connecting to your cluster. If you didn’t copy it, you can reset the password later. Note that you can’t change the generated password, you can only reset it. If you need additional users, you will be able to create them in the Kibana Management app for X-Pack later.

After provisioning of your new cluster is complete, you are redirected to the Overview page for your new cluster:

A newly created cluster in the[Elastic Cloud Console]

You can tell there are a couple of things that need your attention soon: The security features needs to be enabled (on versions before 5.0) and you probably want to enable Kibana, because it’s a great tool for analyzing any type of data stored in Elasticsearch. If you are new to the Elastic Stack, we suggest you hold off for a bit and try connecting to your cluster in the next section first. (If you already enabled the security features or created a version 5.x cluster, don’t worry, we show you how to include authentication details when connecting to your cluster later on. Using authentication is a good thing.)

Before you move on, take note of the links available from the Overview page: Many of the tasks that are described elsewhere in the Elastic Cloud documentation are accessible from these links. For example, to change your cluster later on, simply select Configuration in the sidebar (to learn more about the various configuration parameters, see Cluster Configuration). To work with users and roles, go to Security (in version 5.0 and later, the page links you to the Management app in Kibana). Note that some options are available only if you are on a specific subscription level.

Connect to Your Cluster

From the Overview page for your new cluster in the Elastic Cloud Console, you can click one of the URLs under Endpoints and connect to the cluster in your browser. You should get see a standard message like this:

  "name" : "instance-0000000000",
  "cluster_name" : "a1b2c3d4a1b2c3d4a1b2c3d4a1b2c3d4",
  "cluster_uuid" : "0z2PsOX1TCGSk7PKgB9ajg",
  "version" : {
    "number" : "2.4.1",
    "build_hash" : "c67dc32e24162035d18d6fe1e952c4cbcbe79d16",
    "build_timestamp" : "2016-09-27T18:57:55Z",
    "build_snapshot" : false,
    "lucene_version" : "5.5.2"
  "tagline" : "You Know, for Search"

There are many ways of connecting to an Elasticsearch cluster and we do our best to support them all. Currently we support:


Used by the curl command and most programming languages that aren’t Java. To interact with your cluster, use your Elasticsearch cluster endpoint information from the Overview page in the Elastic Cloud Console. Port 9243 is used for HTTPS connections and is recommended (port 443 is also supported for HTTPS).


Always use secure HTTPS connections over port 9243. We still allow HTTP connections over port 9200, but we recommend against them and no longer list the HTTP endpoint on the cluster Overview page.

If this is your first time using Elasticsearch, you can try out some curl commands to become familiar with the basics. If you’re on an operating system like macOS or Linux, you probably already have the curl command installed. For example, to connect to your cluster from the command line over HTTPS with the curl command:

  "name" : "instance-0000000000",
  "cluster_name" : "a1b2c3d4a1b2c3d4a1b2c3d4a1b2c3d4",
  "cluster_uuid" : "0z2PsOX1TCGSk7PKgB9ajg",
  "version" : {
    "number" : "2.4.1",
    "build_hash" : "c67dc32e24162035d18d6fe1e952c4cbcbe79d16",
    "build_timestamp" : "2016-09-27T18:57:55Z",
    "build_snapshot" : false,
    "lucene_version" : "5.5.2"
  "tagline" : "You Know, for Search"

To make this curl command work with your cluster, you need to replace the cluster ID a1b2c3d4a1b2c3d4a1b2c3d4a1b2c3d4 and the region us-east-1 with the right values from your own endpoint URL. The cluster shown in the example is not publicly accessible.


If you created a cluster on Elasticsearch 5.0 or later or if you already enabled the security features, you must include authentication details with the -u parameter. For example: curl -u elastic:password (Don’t forget to substitute your own cluster ID and your password for the elastic user.)

There is a Quickstart guide in the Cloud console with additional examples that you can copy into your shell to index and retrieve documents in Elasticsearch, for example. Once you experiment with slightly bigger queries, you might also want to try something that is a little more syntax aware. Some popular choices are:

  • Kibana, a great tool for analyzing any type of data stored in Elasticsearch, has grown to include Console, which is useful for interacting with the REST API of Elasticsearch (for version 5.0 and later). In versions before 5.0, Console is called Sense.
  • The query editor in Kopf
  • Elastic-hammer, a web front-end for Elasticsearch.
Java transport client

A good choice if your applications are using Java. This lighter-weight transport client forwards requests to a remote cluster over port 9343 with TLS/SSL (port 9300 without encryption is also supported), using the native Elasticsearch transport protocol.

To learn more about how you can use the Java transport client, typically in conjunction with X-Pack security features or Shield, see Configure the Java Transport Client. There is also an older plugin that is now deprecated.

Access Kibana

Kibana is an open source analytics and visualization platform designed to search, view, and interact with data stored in Elasticsearch indices. The use of Kibana is included with your subscription.

For new Elasticsearch clusters that use version 5.0 and later, we automatically create a Kibana instance for you. If you use a version before 5.0 or if your cluster didn’t include a Kibana instance initially, there might not be a Kibana endpoint URL shown, yet. To gain access, all you need to do is enable Kibana first.

To access Kibana:

  1. Log into the Elastic Cloud Console, if you aren’t logged in already.
  2. Click Clusters at the top and select one of your clusters.
  3. Under Endpoints, click the Kibana endpoint URL and wait for Kibana to open.
  4. Log into Kibana.

    For version 5.0 and later: Log into Kibana with the elastic superuser to try it out. The password was provided when you created your cluster or can be reset.

    For versions before 5.0: and if Shield is enabled, you can log into Kibana with the admin user to try it out. The password was provided when you enabled Shield or can be reset.

In production systems, you might need to control what Elasticsearch data users can access through Kibana, so you need create credentials that can be used to access the necessary Elasticsearch resources. This means granting read access to the necessary indexes, as well as access to update the .kibana index.

Next Steps

Now that you have provisioned your first cluster, try out some additional steps:

  • Enable additional features, such as Shield, Kibana (for clusters that didn’t get a Kibana instance created automatically), monitoring, and more.
  • Configure your cluster by upgrading to a newer Elasticsearch version or adding some plugins, for example.
  • Like what Elastic Cloud can do for you? Add a credit card to continue using the service past your trial expiration date, to add more clusters, or to increase the processing capacity of your existing cluster.
  • Read our blog, which covers topics for both beginners and experienced users.