Elastic Cloud Enterprise 2.8.0edit

We’re starting off the new year with a release that’s all about cleaning house. Just a few smaller features, plenty of enhancements, and squashing some bugs.

This version of Elastic Cloud Enterprise is bundled with our latest Elastic Stack 7.11. To learn more about best practices when upgrading deployments from previous versions of the Elastic Stack, check Upgrade versions.


Add Support portal link. For users with a Support account, the Support page now includes a link to the Elastic Support portal.

Add endpoint for determining supported applications. Add an endpoint listing the applications that the user can access from Okta.

curl -H "Authorization: Bearer $AUTH_TOKEN"

Sample response:

    "applications": [


Add Kibana deep linking to the "waiting" banner link. Adds deep links to the waiting banner - so when you create an Observability deployment, for example, the "Open Kibana" link brings you to the Observability area.

Log delivery create deployment button and clear logs from UI. - Add button to create a monitoring deployment on the Logs and Metrics page when only one or no deployment are available.

Mandatory storage multiplier in instance configuration. A field diskQuotaMultiplier (or API’s storage_multiplier) of Instance configuration becomes mandatory on reading and writing. This does not affect the API contract where that field is optional (but filled out by default taken from settings during the conversion to the persistent model)

Default disk quota multipliers (constructor). The constructor service is updated to recognize default disk quota multipliers for each known cluster type.

The constructor now supports three new environment variables:

  • ES_DISK_QUOTA_MULTIPLIER - Default disk quota multiplier for Elasticsearch instances. If the multiplier is not defined in an instance configuration, this value is used. Optional. The default value is 32.
  • KB_DISK_QUOTA_MULTIPLIER - Default multiplier for Kibana. Optional. The default value is 4.
  • APM_DISK_QUOTA_MULTIPLIER - Default multiplier for APM. Optional. The default value is 4.

Make API keys API endpoint public. You can now manage API keys via the keys API endpoint in addition to managing them through the UI.

Log delivery - No Deployments dropdown. Updates content when enabling monitoring and adds a message No compatible deployments when no deployments are available.

Add dedicated master nodes when autoscaling a cluster. The autoscaling request handler can now perform post-processing of scaled cluster specification and automatically add dedicated masters, if the number of nodes (any combination of roles, other than dedicated masters) exceeds the threshold. The default number of nodes is six and is defined in the cluster settings.

Add account id on deployment alias znode. @Elastic Adds account_id to the zNode for a regional deployment alias in preparation for allowing remapping.

Update Okta profile with ESS User ID. Store ESS user IDs in an Okta’s custom attribute users.essUserId

Add node_roles support to the EsClusterTopologyElement. Add a new nodeRoles field to the EsClusterTopologyElement for Elasticsearch version 7.10 and later.

Add Workplace Search sync monitor configs. Add Workplace Search content source sync error configurations to the configuration allowlist (whitelist).

Add support for reporting metrics to APM via micrometer. Add support for reporting metrics to APM via micrometer.

Bug fixesedit

Fixed container scheduled service connections leak. We added a new container scheduled task service in release 2.7.0 for running miscellaneous administrative tasks on runners with the allocator role. Unfortunately, this new service was causing an excessive number of connections to be created to the ZooKeeper coordination services. This release addresses the resource leak.

Hides messages the deployment is still being created. Hide some transient configuration messages on overview page while a deployment is creating.

Snapshot suspension correction. During plan changes, snapshots are automatically suspended to avoid conflict. Fixes an issue where occasionally snapshotting would remain suspended.

Fix YAML parser in UI. Fixes a bug where attempting to save YAML settings, that only include comments, resulted in an error message: The YAML settings are invalid, please check your syntax.

Remove issue time so that JWT doesn’t change from plan to plan. Fixes an issue where if log delivery is enabled, a force restart of the plan could cause instances to be created.

Configures SSO properly with defaults. If the Elastic Stack version is left out of the API call, the system chooses the latest generally available version. This release fixes an issue where SSO into Kibana was not configured if the Elastic Stack version was left out.

Navigation breadcrumbs not displaying correctly. Fixes the breadcrumbs on the authentication provider screens.

Fix boot looping error message Fixes a misleading error message that claimed an instance is boot looping even if it may not have been.

Fix issue where APM or AppSearch could get flagged valid for SSO. The Cloud Deployments API has a bug fixed where requests to create or update a deployment can fail in some cases when APM resources share the same ref_id value as Kibana or Enterprise Search. The bug caused the API to consider APM valid for SSO, which would result in a failed validation for the updated deployment plan.

Fix JSON search slow logs and deprecation logs. Fixed an issue where, when log delivery is enabled, slow logs are not always ingested.

Fix missing "basic" auth provider For Cloud SSO, a basic username and password form should be displayed when a user does not have any other auth providers configured in the Kibana custom settings. This fixes a bug that earlier could prevent the "basic" provider from being used when SAML realm SSO settings are updated.

Fix missing SSO on deployment update. Fixes a bug where single sign-on (SSO) is not enabled when a new (version 7.7.0 and later) Kibana or (version 7.9.2 and later) Enterprise Search instance is added to a deployment.

Known issuesedit

In some cases, version 7.11 deployments might not detect the XFS quota set in ECE. The quota won’t be exceeded, but deployments may not detect that they are running low on disk space. If you encounter this problem, as a workaround you can upload a new version 7.11 stack pack from our website. Then, open the deployment Edit page and click Save to reapply the current deployment settings with the refreshed stack pack. If you upload a version 7.11.0 stack pack before upgrading to ECE 2.8.0 (or version 7.11.1 before upgrading to ECE 2.8.1) this issue will not occur.

Upgrading to ECE 2.8 will also upgrade the security cluster to Stack version 7.11, where an Elasticsearch known bug may prevent customers from authenticating if they use an AD or LDAP external realm. This will be fixed in an upcoming patch version of Elasticsearch and ECE.