Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Cloud Infrastructure / Amazonaws / Amazon Elasticsearch Service
Amazon Elasticsearch Service logo

AWS Amazon Elasticsearch Service

Browse all Amazonaws APIs
63
AI ReadinessAI-Aware (B-)63/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticCloud InfrastructureComputeapiKey50 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Provision and manage Amazon Elasticsearch (OpenSearch) domains, packages, and cross-cluster connections through a single API.

Use for: I need to create a three-node Elasticsearch domain in a VPC, Update the instance type of an existing domain, List all Elasticsearch domains in this account, Cancel a pending service software update

Not supported: Does not handle index operations, search queries, or document ingestion - use for Elasticsearch and OpenSearch domain configuration only.

Jentic publishes the only available OpenAPI specification for Amazon Elasticsearch Service, keeping it validated and agent-ready. The Amazon Elasticsearch (now OpenSearch) Configuration API creates and manages Elasticsearch domains, including instance configuration, storage, VPC settings, access policies, package associations, and cross-cluster connection setup. The API also covers service software updates, package management, and VPC endpoint authorisation. It is built for platform teams that need to provision and operate search and analytics clusters on AWS without console-driven workflows.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Amazon Elasticsearch Service to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon Elasticsearch Service, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Famazon-elasticsearch-service" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Famazon-elasticsearch-service" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Amazon Elasticsearch Service API.

Create Elasticsearch and OpenSearch domains with custom instance counts, storage, and VPC settings

Manage service software updates and cancel pending update windows

Associate and dissociate packages such as custom dictionaries with running domains

Set up cross-cluster search by creating inbound and outbound connections between domains

Authorize and revoke VPC endpoint access for cross-account domain consumers

Tag and untag domains, packages, and connections for cost allocation

Describe domain change progress to monitor configuration roll-outs

Use Cases

Patterns agents use Amazon Elasticsearch Service API for, with concrete tasks.

★ Search Domain Provisioning

Platform teams use the Amazon Elasticsearch API to provision search and log-analytics domains with VPC isolation, dedicated master nodes, and EBS storage. The API drives domain creation, configuration updates, and access policy management so that infrastructure pipelines can stand up search backends without console clicks. A typical three-node VPC domain provisions in fifteen to thirty minutes, returning a domain endpoint for application connection.

Create an Elasticsearch domain named search-prod with three r5.large.elasticsearch instances and 100 GiB of EBS storage in subnets subnet-a and subnet-b.

Cross-Cluster Search Setup

Data platform teams use cross-cluster connections to query indices that live in separate Elasticsearch domains, often for tenancy or region isolation. The API creates inbound and outbound connections, enabling federated queries without bulk data movement. This pattern keeps shard counts manageable per domain while preserving a single query surface for analysts.

Create an outbound cross-cluster connection from domain search-prod to remote domain search-eu and accept the matching inbound connection.

Service Software Update Coordination

Reliability teams use the API to monitor and time service software updates for Elasticsearch domains so that planned maintenance windows align with low-traffic periods. The API exposes start, schedule, and cancel actions for software updates and surfaces the engine version progress field so dashboards can track fleet-wide patch state. Coordinated updates limit availability impact on customer-facing search.

Cancel the pending service software update on domain search-prod and reschedule it for the next maintenance window.

Agent-Driven Search Cluster Operations via Jentic

AI agents use the Amazon Elasticsearch API through Jentic to manage domain lifecycle, package associations, and software updates as part of larger platform workflows. Jentic exposes Elasticsearch operations as discoverable tools so an agent can search by intent and execute the matching call. This lets a platform agent respond to capacity or version events without console interaction.

Search Jentic for create elasticsearch domain, load the CreateElasticsearchDomain schema, and execute it for a new staging domain with two t3.medium.elasticsearch nodes.

Key Endpoints

50 endpoints — jentic publishes the only available openapi specification for amazon elasticsearch service, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/2015-01-01/es/domain

Create a new Elasticsearch domain

POST

/2015-01-01/packages

Create a custom package such as a synonym list

POST

/2015-01-01/packages/associate/{PackageID}/{DomainName}

Associate a package with a domain

POST

/2015-01-01/es/domain/{DomainName}/authorizeVpcEndpointAccess

Authorize VPC endpoint access

POST

/2015-01-01/es/serviceSoftwareUpdate/cancel

Cancel a pending service software update

POST

/2015-01-01/es/ccs/outboundConnection

Create an outbound cross-cluster connection

POST

/2015-01-01/tags

Add tags to a domain or package

POST

/2015-01-01/es/domain

Create a new Elasticsearch domain

POST

/2015-01-01/packages

Create a custom package such as a synonym list

POST

/2015-01-01/packages/associate/{PackageID}/{DomainName}

Associate a package with a domain

POST

/2015-01-01/es/domain/{DomainName}/authorizeVpcEndpointAccess

Authorize VPC endpoint access

POST

/2015-01-01/es/serviceSoftwareUpdate/cancel

Cancel a pending service software update

POST

/2015-01-01/es/ccs/outboundConnection

Create an outbound cross-cluster connection

POST

/2015-01-01/tags

Add tags to a domain or package

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

A

Amazon Elasticsearch Service

- AI-Aware (B-)
63/100
99
Foundational Compliance
63
Developer Experience & Jentic Compatibility
40
AI-Readiness & Agent Experience
94
Agent Usability
50
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

40

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4
61%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

0%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

50

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1
50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Amazon Elasticsearch Service configuration API by hand means building SigV4 request signing, resolving the regional es.{region}.amazonaws.com host, and handling AWS throttling and retries yourself. Through Jentic you install once, import Elasticsearch Service from the API Directory, store the AWS access keys once, and your agent calls it.

Permission scoping

Elasticsearch Service puts the domain name in the URL path (/2015-01-01/es/domain/{DomainName}/...), so a rule can pin your agent to one domain: it can configure and authorize access for that domain and nothing else. You choose the operations it may call, so domain deletion is not included unless you add it.

Credential isolation

Your AWS access keys for the Elasticsearch Service configuration API are stored once, encrypted, by your own Jentic One instance and injected at execution time when the request is signed. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a search domain' or 'associate a package with a domain', and Jentic returns the matching Elasticsearch Service operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Amazon EC2

→

Manages the VPC subnets and security groups domains run inside

Choose EC2 when you need to inspect or modify the networking configuration that surrounds an Elasticsearch domain.

Complementary

Amazon Kinesis Data Analytics

→

Streams data into Elasticsearch domains in near real time

Choose Kinesis Data Analytics when you need to transform streaming data before indexing into a search domain.

Complementary

AWS Lambda

→

Custom indexing and processing functions in front of Elasticsearch

Choose Lambda when documents need transformation or enrichment before being indexed into a domain.

FAQs

Specific to using Amazon Elasticsearch Service API through Jentic.

Why is there no official OpenAPI spec for Amazon Elasticsearch Service?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon Elasticsearch Service via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Amazon Elasticsearch API use?

The Configuration API uses AWS Signature Version 4 request signing. Through Jentic, AWS access keys are stored encrypted in the vault and signing happens server-side, so the agent never sees the raw secret access key.

Can I create OpenSearch domains with this API?

Yes. POST /2015-01-01/es/domain creates Elasticsearch and OpenSearch domains; the EngineVersion field accepts both Elasticsearch_7.x and OpenSearch_x.y values to select the engine.

What are the rate limits for the Amazon Elasticsearch API?

AWS applies per-account, per-region throttling on the Configuration API. Mutating calls such as CreateElasticsearchDomain are throttled more aggressively than describe calls. Use exponential backoff on ThrottlingException responses; AWS does not publish exact TPS numbers in the spec.

How do I associate a custom synonyms package with a domain through Jentic?

Search Jentic for associate elasticsearch package, load the schema for POST /2015-01-01/packages/associate/{PackageID}/{DomainName}, and execute it with the package ID and domain name. Jentic returns the association status.

Does this API run search queries against indices?

No. This is the configuration API for managing domains. Index and search requests go to the per-domain endpoint URL using the standard Elasticsearch or OpenSearch query DSL.

Can I limit what my agent is allowed to do with the Amazon Elasticsearch Service API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. Since the domain name sits in the URL path (/2015-01-01/es/domain/{DomainName}/...), you can pin the agent to a single domain so it configures and authorizes access for that domain and nothing else. You also choose which calls it may make, so destructive operations like domain deletion stay off the list unless you add them.

GET STARTED

Start building with Amazon Elasticsearch Service API

Explore with Jentic One
View OpenAPI Document