- 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
Securing your deployment
editSecuring your deployment
editThe security of Elasticsearch Add-On for Heroku is described on the Elastic Cloud security page. In addition to the security provided by Elastic Cloud, you can take the following steps to secure your deployments:
-
Prevent unauthorized access with password protection and role-based access control:
-
Reset the
elastic
user password. - Use third-party authentication providers and services like SAML, OpenID Connect, or Kerberos to provide dynamic role mappings for role based or attribute based access control.
- Use Kibana Spaces and roles to secure access to Kibana.
- Authorize and authenticate service accounts for Beats by granting access using API keys.
- Roles can provide full, or read only, access to your data and can be created in Kibana or directly in Elasticsearch. Check defining roles for full details.
-
Reset the
- Block unwanted traffic with traffic filter.
- Secure your settings with the Elasticsearch keystore.
In addition, we also enable encryption at rest (EAR) by default. Elasticsearch Add-On for Heroku supports EAR for both the data stored in your clusters and the snapshots we take for backup, on all cloud platforms and across all regions.
ElasticON events are back!
Learn about the Elastic Search AI Platform from the experts at our live events.
Register nowWas this helpful?
Thank you for your feedback.