Elastic Cloud Enterprise

Commercial self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.

6 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

Elastic Cloud Enterprise 3.8.6 and 4.2.1 security update

ESA-2026-211, 212, 215, 216, 218, 221, and 222 cover credential escalation, retained certificate credentials and CA keys, cross-deployment access through symlinks, role-token exposure, and platform-setting authorization.

Scope: Most issues affect releases through 3.8.5 and 4.2.0. ESA-2026-222 affects 4.1.0 through 4.2.0 when Enterprise Search is present. Fixed releases are 3.8.6 and 4.2.1.

Several issues require particular platform roles, certificate rotation, persistent tokens, symlink paths, or Enterprise Search. Multiple advisories have no workaround.

Action: Upgrade to 3.8.6, 4.2.1, or later; perform certificate cleanup where required; and review or revoke persistent role tokens.

Primary source · ESA-2026-211 · ESA-2026-212 · ESA-2026-215 · ESA-2026-218 · ESA-2026-221 · ESA-2026-222 · Reviewed 2026-11-18

Elastic Cloud Enterprise CVE-2026-114938 guidance

Elastic says affected Elasticsearch on x86-64 AVX512_VBMI CPUs can permit authenticated RCE and unauthenticated denial of service.

Scope: ECE-hosted Elasticsearch 7.17.3 and later on affected hardware; planned ECE 4.2.2 and 3.8.7 were not yet released when reviewed.

CPU features, JDK and deployed Elasticsearch version determine exposure.

Action: Apply -XX:-UseBASE64Intrinsics, restart every deployment and follow Elastic's advisory until fixed ECE images are released and deployed.

Primary source · Reviewed 2026-11-19

What lands where

  1. Supplied by

    Vendor or project

    Official ECE installation script on prepared AWS, Azure or Google Cloud Linux hosts

  2. Operated by

    Your team

    Customer manages cloud instances, Linux and container runtime compatibility, XFS storage, networking, DNS, certificates, host maintenance, capacity, backups, upgrades and licensing.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodOfficial ECE installation script on prepared AWS, Azure or Google Cloud Linux hosts
InfrastructureServers / containers
ECE uses multiple persistent Linux hosts for orchestration, proxies and workload allocators and then runs Elastic Stack clusters on those hosts.
Licensing modelCommercial Only
ECE starts with a 30-day trial and then requires a valid Elastic Cloud Enterprise orchestration license.
LicenseCommercial Elastic Cloud Enterprise license required after the trial.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

6 of 12 fields researched (50%) · 6 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

ECE supports SAML 2.0 Web Browser SSO for the orchestrator/Cloud UI, with attribute and role mappings. It does not apply to ordinary API clients or automatically configure every hosted Elasticsearch/Kibana deployment; those access policies are separate.

Self-managed ECE orchestrator browser federation · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

Current advisory review: ESA-2026-211, 212, 215, 216, 218, 221, and 222 cover credential escalation, retained certificate credentials and CA keys, cross-deployment access through symlinks, role-token exposure, and platform-setting authorization. Upgrade to 3.8.6, 4.2.1, or later; perform certificate cleanup where required; and review or revoke persistent role tokens. Current review: CVE-2026-114938 can affect Elasticsearch 7.17.3 and later on x86-64 AVX512_VBMI CPUs. Authenticated read access can permit RCE and unauthenticated access can cause denial of service. Elastic planned ECE 4.2.2 and 3.8.7 but had not released them when reviewed. Use -XX:-UseBASE64Intrinsics, restart every deployment and follow the vendor advisory until fixed ECE images are available.

ECE-hosted Elasticsearch deployments on affected x86-64 AVX512_VBMI hardware; planned ECE versions are not recorded as released · Source ↗ · Prior security-controls source ↗ · ESA-2026-211 ↗ · ESA-2026-212 ↗ · ESA-2026-215 ↗ · ESA-2026-218 ↗ · ESA-2026-221 ↗ · ESA-2026-222 ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

ECE installation prepares supported Linux hosts, Docker or Podman, XFS quotas and mount points before installing the orchestrator. Follow the supported OS/container-engine matrix and deployment-specific prerequisites; generic cloud VMs alone are insufficient.

Elastic Cloud Enterprise installation guide; orchestrator hosts, not Elastic Cloud Hosted · Source ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

ECE lists an 8-GB installation floor per host role, but recommends 128–256 GB for allocator hosts and distinct control/proxy sizing. HA needs at least three hosts across three availability zones. Fast SSDs, deployment memory/storage ratios and cluster workloads materially affect the footprint; the installer floor is not production capacity.

ECE host-role requirements; hosted deployment capacity and HA additional · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

ECE requires an Elastic-issued licence; installation activates a 30-day trial. A full ECE licence enables managed deployments at the stated Enterprise subscription feature/support level for their stack version. The page does not quote a price; obtain ECE terms separately from hosted Elastic Cloud rates and infrastructure.

Commercial ECE platform/deployment licensing; numeric price requires a quote · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

Elastic Cloud Enterprise 4.2.1 was released October 20, 2026; 3.8.6 is the parallel fixed release for that maintained line. The updates address multiple platform-role, credential, certificate, token, and cross-deployment issues.

Elastic Cloud Enterprise 3.8 and 4.2 maintained lines · Source ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Show all fields (6 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

This entry covers Elastic Cloud Enterprise, not Elastic Cloud Hosted or Elastic Cloud Serverless. ECE requires supported Linux and container-engine combinations, dedicated storage planning and coordinated host maintenance; automatic cloud VM patching can disrupt the platform. Elastic Cloud Enterprise 3.8.6 and 4.2.1 fix seven platform-role, retained credential and CA key, cross-deployment symlink, role-token, and platform-setting issues. Certificate-rotation users must complete the documented cleanup after upgrade, and operators should review or revoke persistent role tokens. Elastic's CVE-2026-114938 advisory states Elasticsearch 7.17.3 and later can be affected on x86-64 AVX512_VBMI CPUs. Authenticated read access can permit RCE and unauthenticated access can cause denial of service. Planned ECE 4.2.2 and 3.8.7 were not yet released at review time; until fixed images are available, apply -XX:-UseBASE64Intrinsics, restart every deployment and follow Elastic's rollout guidance.

Category fit

Data & analytics
Orchestrates self-managed Elasticsearch and Kibana deployments for search, analytical and data-exploration workloads.
Databases & vector
Operates Elasticsearch clusters that provide document, full-text and vector search in customer infrastructure.
Observability
Operates Elastic Stack deployments used to ingest, search and analyze logs, metrics, traces and security telemetry.

Compare within Data & analytics

  • ActivityInfo (Self-Managed Server)Commercial self-managed data collection, relational records and program-reporting platform.
    • Azure
    Customer-operated · Commercial Only
  • Airbyte Self-ManagedSelf-managed data movement and ELT platform with customer-operated connectors and job execution.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Source Available
  • Apache Doris Self-HostedApache-licensed analytical database with upstream AWS EKS/Alibaba ACK/ACS guides and a separately packaged cloudimg Azure VM path.
    • AWS
    • Azure
    • Alibaba Cloud
    Customer-operated · Open Source / Open Core
  • Apache DruidColumn-oriented analytics database for interactive queries over streaming and historical event data.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Apache SupersetBusiness intelligence and data exploration platform for SQL analysis, visualizations and shared dashboards.
    • AWS
    Customer-operated · Open Source / Open Core
  • AVEVA PI System (BYOL)Commercial industrial data collection, historian and visualization system with an AWS architecture.
    • AWS
    Customer-operated · Commercial Only
  • Azure Trusted Research EnvironmentOpen-source reference platform for isolated research workspaces and controlled data movement.
    • Azure
    Customer-operated · Open Source / Open Core
  • Cloud Carbon FootprintOpen-source cloud-usage, energy and carbon-estimation application.
    • Google Cloud
    Customer-operated · Open Source / Open Core

Showing 8 of 43 other listings in Data & analytics. These products address related workflows; read their category-fit notes before comparing scope. See all of Data & analytics →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Elastic Cloud Enterprise on public cloud hosts ↗ · AWS, Azure, Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-15. Vendor support commitment: not assessed; confirm the selected release and contract.

      Elastic's current ECE installation guide explicitly supports public-cloud hosts on AWS, Google Cloud and Microsoft Azure and installs ECE on customer-prepared virtual machines.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory