OpenSearch support

OpenSearch Support for Self-Managed Clusters and Amazon OpenSearch Service

Last reviewed by Tyler Eastridge

AceMQ supports OpenSearch 24/7 across Americas, EMEA and APAC, on self-managed clusters, Amazon OpenSearch Service domains and OpenSearch Dashboards. Most calls start with one of three problems: security plugin role mappings that hide data without any health warning, snapshots that fail on restore, or an upgrade that has been deferred because nobody wants to break access control.

AceMQ supports self-managed OpenSearch and Amazon OpenSearch Service in production — unassigned shards after a blue/green deploy, ISM policies that silently stopped rolling over, fine-grained access control errors nobody can decode, and clients still speaking Elasticsearch 7.10. Every ticket reaches a named senior engineer who knows your cluster.

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

Planning a build, upgrade or migration instead? See AceMQ OpenSearch 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

Missing documents behind a green cluster, snapshots that fail halfway, stuck ISM policies: what each looks like and the API call we make first.

Common OpenSearch production problems and how AceMQ resolves them
Symptom you're seeingWhat we check first
Users see fewer documents than they should, and cluster health is greenCheck the role mapping with GET _plugins/_security/api/rolesmapping and the role's document-level security (DLS) query and field-level security (FLS) lists. A mapping that matches no backend role looks like missing data, not like an outage.
A snapshot restore starts and then fails on specific shardsRun repository verification (POST _snapshot/<repo>/_verify) on every registered repository and read GET _snapshot/<repo>/<snapshot>/_status. Failures usually trace to a repository path that changed or an access policy that covers only part of the bucket.
Index State Management (ISM) is stuck on one stepCheck GET _plugins/_ism/explain/<index>. A policy that applies to new indices only, a rollover alias that points at two write indices or a failed transition leaves one index growing.
Node-to-node TLS errors appear after a certificate changeCheck the transport and HTTP certificates referenced in opensearch.yml and the admin certificate DN list. A certificate that is valid but not listed in plugins.security.authcz.admin_dn blocks securityadmin changes.
Cluster manager elections repeatCheck GET _cat/cluster_manager and the cluster manager node logs for GC pauses and fault detection timeouts. Even node counts in the voting set and a shared small disk are common causes.
Search latency climbs at the 99th percentile on a single indexEnable the search slow log, then run profile: true on the offending query. Wildcard prefixes, scripted scoring and very deep pagination give a flat median with a long tail.
Dashboards saved objects fail to import after an upgradeCheck the saved-object migration output and the .kibana or .opensearch_dashboards index state, then reindex the system index from the last good snapshot.

Every P1 ends in a report naming the shard, mapping, role or policy at fault, and the change that closes it.

Cluster red, ingest backed up, Dashboards unreachable? Request a quote and we answer within an hour.

Contact Us

Deployment coverage

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

DeploymentWhat AceMQ coversWhat the vendor or platform coversExcluded
Self-managed on VMs, bare metal or KubernetesIncidents, shard and mapping design, security plugin, snapshots, upgradesNothing; the project is open sourceDefects that require a change to upstream code
Amazon OpenSearch ServiceIndex design, query cost, ISM, client behaviour, access policiesAWS runs the service, nodes and domain upgrades under AWS SupportFaults in the AWS service layer
Amazon OpenSearch ServerlessCollection design, access policies, client behaviourAWS runs the platformAnything inside the AWS control plane
Air-gapped or regulated estatesOffline upgrade and patch process, security plugin regression testsNot applicableWork needing outbound access we are not given

Support options

Vendor support or independent support for OpenSearch?

OpenSearch has no single vendor to call. It is an open-source project under the Apache 2.0 licence, so support comes from the cloud service you run it on, from commercial providers, or from the community.

What its own page says
Gap to ask about
CommunityDocumentation and forums
CommunityNo response time
AWSAmazon OpenSearch Service advertises 99.99% availability with Multi-AZ with Standby, backed by AWS Support
AWSSupports its own service, not a cluster you run elsewhere
CanonicalOpenSearch with Ubuntu Pro: 24/7 SLA-backed support, up to 15 years of security maintenance
CanonicalResponse times and prices not stated
Instaclustr (NetApp)An OpenSearch support contract with "deep expertise with OpenSearch deployments"
Instaclustr (NetApp)Self-managed coverage and response times not stated
AceMQ24/7 across Americas, EMEA and APAC, response targets from 15 minutes, by plan
AceMQNot an upstream vendor, so no vendor patches

Elastic does not support OpenSearch, so an Elastic subscription does not help if your application talks to OpenSearch.

What's Included

Everything in your OpenSearch support contract

Index design, the security plugin, snapshots, ISM, Dashboards and migrations are covered together, whether the cluster is yours or an Amazon domain.

  • 01

    Emergency Incident Response

    Red cluster, ingest stalled, or Dashboards down for the team that depends on it. 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 shard, mapping, or policy change that prevents a repeat. Delivered as standard, not on request.

  • 03

    Query & Indexing Performance

    Shard sizing, refresh interval and translog durability, mapping design, and query rewrites tuned against your actual traffic mix. We will tell you when the answer is an index template rather than a bigger instance type.

  • 04

    Elasticsearch to OpenSearch Migration

    Snapshot-based migration, client library assessment, the compatibility.override_main_response_version bridge, ILM to ISM policy translation, and rebuilding the Kibana features that OpenSearch Dashboards implements differently.

  • 05

    Amazon OpenSearch Service Operations

    Managed domain sizing, blue/green deploy planning, fine-grained access control and IAM role mapping, UltraWarm and cold tiering, and the storage ceilings that come with each instance family.

  • 06

    Security, CVE & Version Advisory

    Alerts for CVEs affecting your exact OpenSearch version, plus tested upgrade paths across major versions and the security plugin configuration that comes with them.

Why AceMQ

What teams get from one OpenSearch engineer

  • Named Engineers, Zero Cold Start

    The same senior engineers stay on your account. They know your index templates, your ISM policies, and your ingest pattern — so a P1 call opens with diagnosis instead of you re-explaining the environment.

  • No Tier-1 Triage Layer

    You reach a senior OpenSearch engineer directly by phone, email, or Slack. Nobody collects details to pass along, and no escalation approval stands between you and the person who can fix it.

  • We Cover What AWS Support Won't

    AWS will confirm the domain is healthy and the hardware is fine. They will not debug your mapping, rewrite the aggregation that trips your circuit breaker, or redesign your shard strategy. That gap is exactly where we work.

  • Both Sides of the Fork

    We support OpenSearch and Elasticsearch in production, so migration advice comes from operating both rather than from a preference. Sometimes the honest answer is that the fork you are on is fine and the problem is elsewhere.

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

Clusters we look after

Self-managed nodes on EC2, Kubernetes or bare metal, Amazon OpenSearch Service domains and Serverless collections, and clusters sealed off from outside access.

  • Amazon OpenSearch Service (managed)
  • Amazon OpenSearch Serverless
  • Self-managed on AWS (EC2, EKS)
  • Microsoft Azure (AKS)
  • Google Cloud (GKE)
  • Kubernetes & OpenShift
  • VMware vSphere & Tanzu
  • Bare metal & on-premise
  • Air-gapped / no outbound access
  • OpenSearch 1.x, 2.x and 3.x
  • OpenSearch Dashboards
  • Cross-cluster search & replication

Version coverage

OpenSearch versions we support

OpenSearch versions we support
Release lineWhat we do on it
3.x24/7 support, new-cluster design, rolling upgrades
2.x24/7 support and upgrade planning to 3.x
1.x24/7 support and upgrade planning to 2.x
Elasticsearch 7.10 compatible clientsClient inventory and migration testing

Consulting

OpenSearch consulting and professional services

Project work with a written outcome, separate from the support contract. Named deliverables: Elasticsearch to OpenSearch assessment: client and plugin inventory, compatibility test results, and a per-workload migration or stay decision. Security plugin review: role mappings, DLS and FLS rules, tenants and the admin certificate list, tested against real identities. Multi-tenant search architecture: index-per-tenant or shared-index design, with quotas and access boundaries written down. Upgrade plan and rehearsal: plugin compatibility checks, a mirrored staging run and rollback criteria. Snapshot and recovery design: repository layout, verification jobs and a timed restore runbook.

Escalation Path

Your first hour of an OpenSearch outage

A red cluster and a mapping question are not equals. Each severity below has a response clock set by your plan.

  1. From 15 min (by plan)first responseEmergencyProduction down: red cluster with unassigned primaries, no elected cluster manager, ingest stopped, or Dashboards unreachable for the whole team
  2. 1 hourfirst responseCriticalSevere degradation: repeated cluster manager elections, snapshot restores failing on shards, p99 search latency far above the median
  3. 4 hoursfirst responseHighISM policies stuck on a step, role mappings hiding documents from users, TLS failures after a certificate change
  4. Next Dayfirst responseStandardQuestions on shard sizing, index templates, saved-object migration and Elasticsearch to OpenSearch planning

Plan and severity set each clock, so a red cluster is answered ahead of a question about refresh intervals.

Looking for OpenSearch cover with an engineer who knows your index templates? Get a quote or send a note.

Contact Us

Pricing

What does AceMQ OpenSearch support cost?

OpenSearch support is typically $24,000–72,000 a year. Data node count, whether you use Amazon domains or your own hosts, the security plugin setup and your chosen response plan decide the quote.

Prices are USD. Response targets start at 15 minutes by plan, 24/7, and quote requests are answered within 1 hour. A shared contract across several of your technologies qualifies for a multi-technology discount.

Support In Practice

OpenSearch cases on file

Typical OpenSearch support and remediation engagements. Each card links to the scenario: the cluster or domain, what AceMQ checks or changes, and what the engagement delivers.

  • Remediation

    OpenSearch Snapshot Restore Failure Remediation

    Insurance Services Provider

    Emergency recovery of an OpenSearch domain where snapshot restores were failing partway through and leaving indices in a red state.

    OpenSearchAmazon S3OpenSearch DashboardsLinux
  • Assessment

    Elasticsearch to OpenSearch Migration Assessment

    Digital Media Platform

    Assessment of the technical and licensing implications of moving a large Elasticsearch estate to OpenSearch, including client and plugin compatibility.

    OpenSearchElasticsearchAmazon S3Terraform
All use cases

Support options

Four tiers of OpenSearch support.

AceMQ offers OpenSearch support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for clusters and domains your team runs, proactive monitoring that catches shard, ISM and storage problems first, managed OpenSearch on your own infrastructure, and fully managed OpenSearch on AceMQ infrastructure. OpenSearch 1.x, 2.x and 3.x are covered, self-managed or on Amazon OpenSearch Service.

  • Tier 1

    OpenSearch 24/7 Support & Incident Management

    You operate the cluster, we answer the hard tickets

    Best for: Search and platform teams that need an expert on call when shards, snapshots or security settings misbehave.

  • Tier 2

    OpenSearch 24/7 Support with Proactive Monitoring

    We audit shards, ISM and snapshots on a schedule

    Best for: Teams who want restore tests and policy checks before the day a snapshot is needed.

  • Tier 3

    Managed OpenSearch on Your Infrastructure

    We run your nodes and Dashboards in place

    Best for: Organizations that keep OpenSearch inside their own accounts and networks but want it operated by specialists.

  • Tier 4

    Fully Managed OpenSearch on AceMQ Infrastructure

    We run the OpenSearch nodes and Dashboards for you

    Best for: Product teams that want search and log analytics available without owning cluster operations.

FAQ

OpenSearch support questions

Still have questions about OpenSearch? Email an Expert

Who provides enterprise support for OpenSearch?

There is no single vendor. AWS supports Amazon OpenSearch Service, commercial providers sell support contracts, and AceMQ supports self-managed clusters and Amazon domains 24/7.

Does AWS Support cover my OpenSearch tuning problems?

AWS Support covers the service. Index design, shard strategy, query cost and access policies stay with you, which is where we help.

Why do users see fewer documents than expected?

Usually a role mapping or document-level security query that matches fewer identities than intended. Cluster health will not show it.

Can we move from Elasticsearch 7.10 to OpenSearch?

Yes. OpenSearch is wire compatible with 7.10 clients, but newer Elasticsearch clients include a product check that refuses OpenSearch, so the client inventory comes first.

How do we test that snapshots actually restore?

Run repository verification, then restore a representative index to a scratch cluster on a schedule and alert on failure.

Do you support OpenSearch Dashboards?

Yes, including saved-object migrations, tenants and authentication.

How fast do you respond to an OpenSearch outage?

Response starts within 15 minutes on the top plans, at any hour. A typical Sev 1 is a red cluster after a node loss: an engineer joins a bridge, reads GET _cluster/allocation/explain for the unassigned primaries, and you get a written root cause afterward. P2 is 1 hour, P3 4 hours, P4 next business day.

Do you support OpenSearch Serverless?

We support collection design, access policies and client behaviour. AWS runs the platform.

Is a yearly OpenSearch agreement required?

No. Snapshot restore testing, a migration assessment from Elasticsearch or a security plugin review can each be bought as a standalone engagement. Teams that want 24/7 response and engineers who remember their index templates move to the yearly agreement afterward.

How is an OpenSearch support contract priced?

Most contracts sit between $24,000 and $72,000 a year (USD). The inputs are the number of nodes and clusters, self-managed hosts versus Amazon OpenSearch Service, whether cross-cluster replication or Dashboards multi-tenancy is in play, and your response plan. Describe the estate and a quote arrives within 1 hour.

Let's talk

Your OpenSearch Cluster Is Only as Good as Who Answers at 3am

Tell us where your OpenSearch runs and which version. We reply with a quote within 1 hour.

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

Production incident right now?Email an OpenSearch Architect