Restrictions and known problems

When using Elasticsearch Service, there are some limitations you should be aware of:

Occasionally, we also publish information about Known problems with our Elasticsearch Service or the Elastic Stack.

To learn more about the features that are supported by Elasticsearch Service, see Elastic Cloud Subscriptions.

Elasticsearch Service

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 Service Console, you can use it.

Elastic Stack

  • 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.

Transport client

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 Service are behind proxies, which prevent the transport client from communicating directly with Elasticsearch clusters.

Elasticsearch and Kibana plugins

  • Kibana plugins are not supported.
  • Some Elasticsearch plugins do not apply to Elasticsearch Service. For example, you won’t ever need to change discovery, as Elasticsearch Service 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 Service 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)

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 subscriptions

Cross-cluster search unavailable for AWS Marketplace subscriptions

  • You cannot spin up a cross-cluster search deployment hosted on Elasticsearch Service. Cross-cluster search functionality is not supported.
  • For billing differences, see AWS Marketplace billing.

Known problems

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.

It is not possible to upgrade an App Search deployment to a version above 7.6 without migrating to Enterprise Search. Currently, in case Elasticsearch is upgraded to a version higher than 7.6, you will be met with an Upgrade notification for App Search to match the Elasticsearch version, which cannot be fulfilled as there is no matching App Search version. Beginning with Elastic Stack version 7.7, App Search and Workplace Search are bundled together. In the future, both products will be available as a single Elastic Enterprise Search deployment on the Elasticsearch Service. In order to provide an easier transition to Enterprise Search, we will also add an assistant to help users move from their 7.6 App Search deployments to Elastic Enterprise Search deployments.

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.