Now that you have provisioned your first deployment and indexed some basic documents into your Elasticsearch cluster, you’re ready to do more with your deployment.
Get data into the deploymentedit
There are several ways to ingest data into the deployment:
- Use the sample data available from the Kibana home page in versions 6.4.0 and later, without loading your own data. There are multiple data sets available and you can add them with one click.
- Configure Beats and Logstash to send data to Elasticsearch Service quickly with your Cloud ID.
- If you added an APM Server, configure your APM Agents to return data to your Elasticsearch cluster.
- Got existing Elasticsearch data? Consider your migration options.
You might want to add more layers of security to your deployment, such as:
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, see this article.