Elasticsearch support

Elasticsearch Support for Self-Managed, ECK and Elastic Cloud Clusters

Last reviewed by Tyler Eastridge

AceMQ supports Elasticsearch 24/7 across Americas, EMEA and APAC on self-managed nodes, Elastic Cloud on Kubernetes (ECK) and Elastic Cloud deployments. Most calls begin with one of three problems: a cluster that will not return to green after a node loss, heap pressure that trips circuit breakers, or a major-version upgrade that has to happen without losing search.

AceMQ runs Elasticsearch in production for search, log analytics, and security data lakes — red clusters after a node loss, circuit breakers tripping under aggregation load, oversharded indices bloating cluster state, and ILM policies that quietly stopped rolling over. Every ticket reaches a named senior engineer who already has your cluster topology in their head.

Support quotes answered within 1 hour, by a senior engineer.

Planning a build, upgrade or migration instead? See AceMQ Elasticsearch consulting and services.

160+
Customers supported
10+
Years in production support
40+
Sev 1 incidents handled a year
24/7
Americas, EMEA and APAC
1hour
Quote reply

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Incident Triage

Problems we fix every week

Yellow after every restart, one hot data node, quiet snapshot failures: the symptom as users report it and the request we send first.

Common Elasticsearch production problems and how AceMQ resolves them
Symptom you're seeingWhat we check first
A restarted node takes the cluster through minutes of yellowCheck GET _cluster/health?level=indices and GET _cat/recovery?active_only=true. Common causes are index.unassigned.node_left.delayed_timeout set too low for a rolling restart, or recovery limits (indices.recovery.max_bytes_per_sec, cluster.routing.allocation.node_concurrent_recoveries) left at values that suit neither the network nor the query load.
One data node runs hot while the others idleCheck GET _cat/allocation?v and GET _cat/shards?v&s=store:desc. A few very large shards, or time-based indices whose newest shards all land on the same node, defeat the balancer. The fix is shard sizing and allocation awareness, not another node.
Search requests are rejected while CPU looks fineCheck GET _cat/thread_pool/search?v&h=node_name,active,queue,rejected against the request pattern. A burst of concurrent dashboard refreshes, or one client without a timeout, fills the queue long before the hardware is busy.
Snapshot lifecycle policies fail quietlyCheck GET _slm/policy for last_failure and GET _snapshot/_all. A policy that has been failing for two weeks means the last restorable copy is older than anyone assumes.
Nodes stop talking after a certificate rotationCheck GET _ssl/certificates for expiry dates on the transport and HTTP layers, then the node logs for handshake errors. Transport certificates are the ones that expire unnoticed, because clients still connect over HTTP while the cluster quietly splits.
Cross-cluster search or replication stops after a network changeCheck GET _remote/info for connected: false, then proxy mode versus sniff mode and the seed addresses in the remote cluster settings.
An upgrade stalls on deprecations nobody listedRun GET _migration/deprecations and the Kibana Upgrade Assistant on the current version, then test clients and ingest pipelines against the target before the first rolling step.

P1s end with a written root cause that names the shard, setting or certificate responsible and what to change.

Searches failing in production and the cluster is red? Ask for a quote and we reply within the hour.

Contact Us

Deployment coverage

Which Elasticsearch deployments does AceMQ support, and who covers what?

DeploymentWhat AceMQ coversWhat the vendor or platform coversExcluded
Self-managed on VMs or bare metalIncidents, shard and mapping design, JVM and OS tuning, upgrades, security configurationNothing, unless you also hold an Elastic subscriptionDefects that need a patch to Elastic's own code
ECK on KubernetesCluster behaviour, operator and StatefulSet issues, storage classes, rolling changesElastic covers the operator and product defects under a subscriptionYour Kubernetes control plane
Elastic CloudIndex and mapping design, query cost, ILM, client behaviourElastic runs the service, nodes and platform faultsFaults in Elastic's service layer
Air-gapped or regulated estatesOffline upgrade paths, certificate and keystore handling, runbooksNot applicableAnything needing outbound access we are not given

One contract can span several rows.

Support options

Elastic subscription or independent support: what is the difference?

Elastic subscription
AceMQ independent support
Who answersElastic's support team
Who answersAceMQ senior engineers, assigned to your account
Response targetsEnterprise and Platinum: 24x7x365, 1 hour for Level 1. Gold: business hours, 4 business hours for Level 1
Response targets24/7, from 15 minutes, by plan
ScopeInstallation help, basic configuration, developer guidance; excludes production development support, third-party integrations and security incident investigation
ScopeOperating the cluster you run: incidents, tuning, upgrades, reviews
Product patchesYes, for supported versions under the Enterprise and Platinum tiers
Product patchesNo vendor patches
PricingSelf-managed pricing is not public; Elastic says it is based on nodes and used RAM
Pricing$24,000 to $72,000 a year (USD), by SLA, scope and deployment

Many teams hold both. The subscription covers the product; independent support covers operations. Sources are listed at the foot of the page.

Licence question?

Unsure what the Elastic licence means for support? Start here

The licence decides what you may do with the software, not who can support your cluster.

What's Included

Everything in your Elasticsearch support contract

Cluster architecture, shard and mapping design, snapshots and SLM, security certificates and upgrades are handled under one Elasticsearch agreement.

  • 01

    Emergency Incident Response

    Red cluster, ingest stalled, or search returning errors to production traffic. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge with access to diagnose — not an automated ticket acknowledgement.

  • 02

    Root Cause Analysis

    Every P1 closes with a written RCA: what failed, why, the fix applied, and the mapping, shard, or JVM change that stops it happening again. Delivered as standard, not on request.

  • 03

    Query & Indexing Performance

    Shard sizing, refresh and translog settings, mapping design, filter caching, and query rewrites. We tune against your real query mix rather than a benchmark, and we tell you when the fix is an index template rather than more nodes.

  • 04

    Cluster Architecture Review

    Dedicated master, data, and coordinating roles; discovery and quorum settings that survive a zone loss; hot-warm-cold tiering; and shard allocation awareness. Master election problems are usually design problems.

  • 05

    Security, CVE & Upgrade Advisory

    Alerts for CVEs affecting your exact Elasticsearch version, plus tested upgrade paths across major versions — including the mapping and API breaking changes that make 7.x to 8.x more than a package bump.

  • 06

    Elastic Cloud & Managed Deployments

    We support Elastic Cloud, ECK on Kubernetes, and self-managed clusters. The managed tiers remove node maintenance but not shard strategy, mapping design, or query cost — which is where most incidents actually start.

Why AceMQ

Why Elasticsearch teams stay with one engineer

  • Named Engineers, Zero Cold Start

    The same senior engineers stay on your account. They know your index templates, your shard counts, and your ingest pattern — so a P1 call opens with diagnosis instead of twenty minutes explaining your cluster layout.

  • No Tier-1 Triage Layer

    You reach a senior Elasticsearch engineer directly by phone, email, or Slack. Nobody collects information to pass along, and there is no escalation approval sitting between you and the person who can fix it.

  • We Fix the Data Model, Not Just the Cluster

    Most Elasticsearch incidents trace back to mappings, shard strategy, or a query nobody costed. We work at that layer — analyzers, field types, ingest pipelines, index lifecycle — not only at the node and JVM level.

  • Genuine Follow-the-Sun Coverage

    Round-the-clock coverage for customers in 26+ countries. Your 3am cluster red is someone's mid-afternoon — no overnight skeleton crew, no waiting for a region to come online.

  • Proactive, Not Just Reactive

    Quarterly cluster health reviews plus shared intelligence across our support base. When a version-specific bug surfaces on one customer's cluster, every affected customer hears about it before it reaches their production.

  • Full Stack Around the Cluster

    We diagnose across the ingest path, the JVM, storage latency, and Kubernetes scheduling — because a cluster that goes red at 4am is often a disk or a noisy neighbour rather than Elasticsearch itself.

Elasticsearch estates in scope

Self-managed nodes, ECK operators on Kubernetes, Elastic Cloud deployments, multi-region clusters, and environments that never reach the internet.

  • Elastic Cloud (Elasticsearch Service)
  • Elastic Cloud on Kubernetes (ECK)
  • AWS (EC2, EKS, EBS gp3/io2)
  • Microsoft Azure (AKS)
  • Google Cloud (GKE)
  • Kubernetes & OpenShift
  • VMware vSphere & Tanzu
  • Bare metal & on-premise
  • Hybrid & multi-region clusters
  • Air-gapped / no outbound access
  • Elasticsearch 7.x and 8.x
  • Cross-cluster search & replication

Version coverage

Elasticsearch versions we support

Elasticsearch versions we support
Release lineWhat we do on it
9.x24/7 support, new-cluster design, rolling upgrades within 9.x
8.x24/7 support and upgrade to 9.x
7.17.x24/7 support and the required step to 8.19 before 9.x
7.10.x and earlier24/7 support and upgrade planning

Defects that need a change to Elastic's own code go to Elastic if you hold a subscription. We reproduce, document and work around them.

Consulting

Elasticsearch consulting and professional services

Consulting is project work with a written outcome, separate from the support contract. Named deliverables: Cluster health check: a written review of shard layout, mappings, heap, disk watermarks, thread pools and snapshot state, with a ranked fix list. Shard and index lifecycle design: target shard sizes, rollover and ILM policies, hot-warm-cold tiering, with a sequenced migration plan. Upgrade plan and rehearsal: a deprecation inventory, a tested path (for example 7.17 to 8.19 to 9.x), client and pipeline test results, and a rollback position at each step. Elasticsearch to OpenSearch assessment: client, plugin and feature inventory, with a cost comparison on your node counts. See the OpenSearch support page. Runbooks and on-call handover: the recovery procedures that worked, written so your own engineers can run them.

Escalation Path

Your first hour of an Elasticsearch outage

A cluster rejecting production searches gets answered ahead of a template question. Response clocks follow your plan and the severity below.

  1. From 15 min (by plan)first responseEmergencyProduction down: red cluster, no elected master, ingest stopped, or search errors reaching customer-facing traffic
  2. 1 hourfirst responseCriticalSevere degradation: search thread pool rejections, one overloaded data node, heap pressure triggering long GC pauses
  3. 4 hoursfirst responseHighProlonged yellow after restarts, failing SLM snapshots, transport certificate expiry, cross-cluster links disconnected
  4. Next Dayfirst responseStandardQuestions on shard sizing, ILM policies, index templates, ECK changes and 7.x to 8.x upgrade planning

Plan and severity decide the response clock, so rejected searches and a mapping question land in separate queues.

Want an engineer on call who has already read your shard layout? Request a quote or contact us.

Contact Us

Pricing

What does AceMQ Elasticsearch support cost?

Elasticsearch support typically costs $24,000–72,000 a year. Quotes follow data and master node counts, ECK or Elastic Cloud use, how much data sits in hot, warm and cold tiers, and the response plan.

All figures are in US dollars (USD). Response targets start at 15 minutes by plan, 24/7, and quote requests are answered within 1 hour. A contract that spans more than one technology earns a multi-technology discount.

Support In Practice

Elasticsearch incidents we have worked

Elasticsearch support and remediation work from AceMQ. Each card links to the full write-up: the cluster, what AceMQ diagnosed or changed, and the result.

All use cases

Support options

Four tiers of Elasticsearch support.

AceMQ offers Elasticsearch support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for clusters your team runs, proactive monitoring that catches shard, heap and ILM problems first, managed Elasticsearch on your own infrastructure, and fully managed Elasticsearch on AceMQ infrastructure. Versions 7.x and 8.x are covered, with OSSeva patched builds for 7.10.2 and 7.17.

  • Tier 1

    Elasticsearch 24/7 Support & Incident Management

    Your team owns the cluster, we handle the escalations

    Best for: Engineers who run Elasticsearch day to day and want a senior specialist when allocation or heap problems stop them.

  • Tier 2

    Elasticsearch 24/7 Support with Proactive Monitoring

    Periodic reviews of shards, mappings and snapshots

    Best for: Teams that prefer finding a failing SLM policy or an expiring transport certificate on a calendar, not during an outage.

  • Tier 3

    Managed Elasticsearch on Your Infrastructure

    We operate nodes and ECK in your environment

    Best for: Companies that must keep Elasticsearch on their own infrastructure and still want specialists running it.

  • Tier 4

    Fully Managed Elasticsearch on AceMQ Infrastructure

    We run your search cluster, shards and all

    Best for: Teams that want search and log analytics working, with templates, ILM and capacity handled for them.

FAQ

Elasticsearch support questions

Still have questions about Elasticsearch? Email an Expert

Who provides enterprise support for Elasticsearch?

Elastic sells support only through a subscription. Independent providers such as AceMQ support self-managed clusters, ECK and Elastic Cloud deployments. Many teams hold both: the subscription for product defects, independent support for operations.

What does an Elasticsearch health check include?

A read-only review of cluster health and allocation, shard count and size by index pattern, mapping size against field limits, heap and GC behaviour, disk watermarks, thread pool rejections, snapshot and SLM state, certificate expiry and the deprecation list for the next upgrade. You receive a ranked fix list within the agreed window. A quote reply arrives within 1 hour.

How do you plan an Elasticsearch upgrade without downtime?

Run the deprecation API and Upgrade Assistant first, reindex or mark read-only any indices created before 8.0, upgrade a test cluster with real clients and pipelines, then take a snapshot and perform a rolling upgrade node by node with shard allocation controlled. From 7.17 the path goes through 8.19 before 9.x. Each step has a rollback position agreed beforehand.

What do Elasticsearch managed services include (and what stays with your team)?

In a managed engagement AceMQ runs day-2 operations on a cluster in your own environment: monitoring, paging, patching and upgrades, index templates and ILM, snapshot restore tests and capacity planning. Your team keeps ownership of the data, the application queries and access decisions.

Can you support Elasticsearch on ECK?

Yes. We cover cluster behaviour, StatefulSet and storage class problems and rolling changes. Operator defects go to Elastic if you hold a subscription.

Why does my cluster go yellow after every restart?

Usually replicas wait on a delayed allocation timer, or recovery runs slower than the restart cadence. We tune the delay and recovery limits to the rolling-restart procedure.

How fast do you respond to an Elasticsearch outage?

Response starts within 15 minutes on top plans, 24/7. Consider a Sev 1 where search requests are rejected: an engineer joins a bridge, checks _cat/thread_pool/search for queue and rejected counts, finds the client or burst behind it, and writes the root cause afterward. P2 is 1 hour, P3 4 hours, P4 next business day.

Does Elastic support OpenSearch?

No. OpenSearch is a separate Apache 2.0 project. We support both.

Can we buy Elasticsearch help without a long contract?

Yes. A health check, a 7.x to 8.x upgrade rehearsal or a shard redesign can be bought as a standalone piece of work. When the cluster becomes business critical, the same engineers move you to an annual agreement with 24/7 response.

What sets the price of Elasticsearch support?

Annual contracts usually run $24,000 to $72,000 (USD), not per incident. We scope by node roles and counts, how many clusters you operate, ECK or Elastic Cloud versus self-managed, tiering with ILM, and the response plan. Send those details and the quote reply comes within 1 hour.

Let's talk

A Red Cluster at 3am Shouldn't Be Your On-Call's Problem Alone

Send your cluster size and version. We reply with a quote within 1 hour and, if you want, start with a health check before the first outage.

A senior Elasticsearch engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership

Production incident right now?Email an Elasticsearch Architect