When using Elasticsearch Add-On for Heroku, there are some limitations you should be aware of:
- Elasticsearch Add-On for Heroku
- Elastic Stack
- Transport client
- Elasticsearch and Kibana plugins
- Alerting (formerly Watcher)
- APM with AWS Marketplace subscriptions
- APM Agent central configuration with PrivateLink or traffic filters
- Enterprise Search and AWS Marketplace subscriptions
- Known problems
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.
Elasticsearch Add-On for Herokuedit
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.
- 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.
- Traffic filters must not be enabled on monitoring clusters. If you are shipping your logs or metrics to a monitoring cluster, do not associate traffic filters with the Elasticsearch cluster you are sending the logs or metrics to. Since you cannot explicitly allow traffic from certain clusters currently, associating traffic filters with your monitoring cluster will result in clusters being blocked when sending data.
- LDAP and Active Directory realms are not supported. Alternatively, authentication protocols such as SAML, OpenID Connect, or Kerberos can be used.
- Audit logging is disabled.
- Client certificates, such as PKI certificates, are not supported.
- Traffic filters cannot be used for monitoring clusters, clusters used for storing leader indices for cross-cluster replication, or clusters that are searched across as part of cross-cluster search.
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.
Elasticsearch and Kibana pluginsedit
- 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.
Alerting (formerly Watcher)edit
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.
APM with AWS Marketplace subscriptionsedit
- 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.
APM Agent central configuration with PrivateLink or traffic filtersedit
Cross-cluster search unavailable for AWS Marketplace subscriptionsedit
- You cannot spin up a cross-cluster search deployment hosted on Elasticsearch Add-On for Heroku. Cross-cluster search functionality is not supported.
Enterprise Search unavailable for AWS Marketplace subscriptionsedit
- If you have an AWS Marketplace subscription, you cannot spin up an Enterprise Search deployment hosted on Elasticsearch Add-On for Heroku.
- There is a known problem affecting clusters with versions 7.7.0 and 7.7.1 due to a bug in Elasticsearch. Although rare, this bug can prevent you from running plans. If this occurs we recommend that you retry the plan, and if that fails please contact support to get your plan through. Because of this bug we recommend you to upgrade to version 7.8 and higher, where the problem has already been addressed.
- A known issue can prevent direct rolling upgrades from Elasticsearch version 5.6.10 to version 6.3.0. As a workaround, we have removed version 6.3.0 from the Elasticsearch Add-On for Heroku console for new cluster deployments and for upgrading existing ones. If you are affected by this issue, see Rolling upgrades from 5.6.x to 6.3.0 fails with "java.lang.IllegalStateException: commit doesn’t contain history uuid" in our Elastic Support Portal. If these steps do not work or you do not have access to the support portal, you can contact email@example.com.