- Introducing Elasticsearch Add-On for Heroku
- Configuring your deployment
- Securing your deployment
- Monitoring your deployment
- How to set up monitoring
- Access performance metrics
- Keep track of deployment activity
- Diagnose unavailable nodes
- Why are my shards unavailable?
- Why is performance degrading over time?
- Is my cluster really highly available?
- How does high memory pressure affect performance?
- Why are my cluster response times suddenly so much worse?
- How do I resolve deployment health warnings?
- How do I resolve node bootlooping?
- Snapshot and restore
- About
- Subscription levels
- Version policy
- Elasticsearch Add-On for Heroku hardware
- Elasticsearch Add-On for Heroku GCP instance configurations
- Elasticsearch Add-On for Heroku GCP default provider instance configurations
- Elasticsearch Add-On for Heroku AWS instance configurations
- Elasticsearch Add-On for Heroku AWS default provider instance configurations
- Elasticsearch Add-On for Heroku Azure instance configurations
- Elasticsearch Add-On for Heroku Azure default provider instance configurations
- Elasticsearch Add-On for Heroku regions
- Service status
- Getting help
- Restrictions and known problems
- What’s new with the Elastic Stack
Next steps
editNext steps
editNow that you have provisioned your first deployment, you’re ready to index data into the deployment and explore the advanced capabilities of Elasticsearch Add-On for Heroku.
Index data
editIt’s why you’re here right? You’re looking to solve an issue or improve your experience with your data.
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.
- Got existing Elasticsearch data? Consider your migration options.
Increase security
editYou might want to add more layers of security to your deployment, such as:
- Add more users to the deployment with third-party authentication providers and services like SAML, OpenID Connect, or Kerberos.
- 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
elasticpassword.
Scale or adjust your deployment
editYou 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.
Was this helpful?
Thank you for your feedback.