When using Elasticsearch Add-On for Heroku, there are some limitations you should be aware of:
Occasionally, we also publish information about Known problems with our Elasticsearch Add-On for Heroku or the Elastic Stack.
To learn more about the features that are supported by Elasticsearch Add-On for Heroku, see Elastic Cloud Subscriptions.
Not all features of our Elasticsearch Service are available to Heroku users. Specifically, you cannot create additional deployments or use different deployment templates.
Generally, if a feature is shown as available in the Elasticsearch Add-On for Heroku console, you can use it.
- Cross-cluster replication is not supported.
- Dedicated ingest nodes are not supported.
- To avoid compatibility issues between versions, the cluster sending monitoring metrics and the monitoring cluster receiving them should be at the same Elasticsearch version. If using the same version is not feasible, check for breaking changes in the X-Pack Release Notes or the Marvel Release Notes to make sure that your versions are compatible.
- Monitoring across regions is not supported. If you need to move your existing monitoring to the same region, you can do a reindex or create a new cluster and select the snapshot from the old cluster.
- Monitoring data that gets sent to a dedicated monitoring Elasticsearch cluster is not cleaned up automatically and might require some additional steps to remove excess data periodically.
- IP filtering with the X-Pack or Shield security features is currently not available.
- LDAP is not supported.
- Audit logging is disabled.
- Client certificates, such as PKI certificates, are not supported.
The transport client is not considered thread safe in a cloud environment. We recommend that you use the Java REST client instead. This restriction relates to the fact that your deployments hosted on Elasticsearch Add-On for Heroku are behind proxies, which prevent the transport client from communicating directly with Elasticsearch clusters.
- Kibana plugins are not supported.
- Some Elasticsearch plugins do not apply to Elasticsearch Add-On for Heroku. For example, you won’t ever need to change discovery, as Elasticsearch Add-On for Heroku handles how nodes discover one another.
- In Elasticsearch 5.0 and later, site plugins are no longer supported. This change does not affect the site plugins Elasticsearch Add-On for Heroku might provide out of the box, such as Kopf or Head, since these site plugins are serviced by our proxies and not Elasticsearch itself.
- In Elasticsearch 5.0 and later, site plugins such as Kopf and Paramedic are no longer provided. We recommend that you use our cluster performance metrics, X-Pack monitoring features and Kibana’s (6.3+) Index Management UI if you want more detailed information or perform index management actions.
Changing the default throttle period is not possible. You can specify a throttle period per watch, however.
You cannot use your own SMTP server. All emails are sent through our servers, and the recipient must be whitelisted.
- You cannot spin up an APM Server as part of a deployment hosted on Elasticsearch Add-On for Heroku. If you want to use APM, you can still host it on your own host and connect it to your Cloud deployment. To learn more, see Configure the output for the Elastic Cloud.
- You cannot spin up a cross-cluster search deployment hosted on Elasticsearch Add-On for Heroku. Cross-cluster search functionality is not supported.
There is a known issue affecting 5.6.10 to 6.3.0 upgrades. A fix is available in a later version of the Elastic Stack or you can open a support ticket to receive help.