Next stepsedit

Now that you have provisioned your first deployment, you’re ready to index data into the deployment and explore the advanced capabilities of Elasticsearch Service.

Index dataedit

It’s why you’re here right? You’re looking to solve an issue or improve your experience with your data.

If you haven’t already, you can index, also known as ingest, data into a deployment in several ways. Check them out in Indexing data into Elasticsearch.

Increase securityedit

You might want to add more layers of security to your deployment, such as:

  • Add an MFA device.
  • Add more users to the organization account or just the deployment:

  • Do not use clients that only support HTTP to connect to Elastic Cloud. If you need to do so, you should use a reverse proxy setup.
  • Create traffic filters and apply them to your deployments.
  • If needed, you can reset the elastic password.

Scale or adjust your deploymentedit

You might find that you need a larger deployment for the workload. Or maybe you want to upgrade the Elasticsearch version for the latest features. Perhaps you’d like to add some plugins, enable APM, or machine learning. All of this can be done after provisioning by changing your deployment configuration.

Make it officialedit

Like what Elasticsearch Service 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.

To upload scripts, we ask that you either add a credit card or link: open a support ticket for help. This is simply because we don’t want to run your code without knowing who you are. To find out more about why we do this, check this article.