Restrictions and known problemsedit

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.

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.

Elastic Stackedit

  • Cross-cluster replication is not supported.

Securityedit

  • 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.
  • You can’t set the Watcher webhook target to a deployment protected by traffic filters. Public webhooks such as Slack, PagerDuty, and email are not affected by this limitation.

Transport clientedit

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.

The transport client is not supported over private link connections. Use the Java REST client instead, or connect over the public internet.

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.

Watcheredit

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.

Known problemsedit