Amazon CloudSearch
Amazon CloudSearch is a managed search service that makes it easy to set up, manage, and scale a search solution for your website or application. Supports full-text search, Boolean search, faceted search, autocomplete, geospatial search, and 34 languages.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Amazon CloudSearch the way a machine reads it — 51 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Amazon CloudSearch scores 55.4/100 (developing), with a separate agent-readiness read of 39/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Amazon CloudSearch
Each block below is one kind of artifact we hold for Amazon CloudSearch. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 2
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Amazon CloudSearch Domains API
Operations for creating and managing search domains
Amazon CloudSearch Index Fields API
Operations for defining and managing index fields
Features 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Managed Search Infrastructure
Set up, manage, and scale search without becoming a search expert.
Multi-Language Support
Full-text search across 34 languages with language-specific analyzers.
Faceted Search
Narrow search results by category with faceted navigation.
Autocomplete Suggestions
Real-time search suggestions as users type.
Automatic Scaling
Automatically scale resources as data volume and query traffic change.
High Availability
Distribute search traffic across multiple availability zones with Multi-AZ.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Amazon Cloudsearch Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Amazon CloudSearch API Rules
SPECTRALAmazon CloudSearch API Rules
SPECTRALJSON Schema 10
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Amazon CloudSearch Domain
JSON SCHEMACreateDomainRequest
JSON SCHEMACreateDomainResponse
JSON SCHEMADefineIndexFieldRequest
JSON SCHEMADefineIndexFieldResponse
JSON SCHEMADeleteDomainResponse
JSON SCHEMADescribeDomainsResponse
JSON SCHEMADescribeIndexFieldsResponse
JSON SCHEMADomainStatus
JSON SCHEMAIndexDocumentsResponse
JSON SCHEMAScroll within the panel for all 10 ·
JSON Structure 9
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Cloudsearch Create Domain Request Structure
JSON STRUCTURECloudsearch Create Domain Response Structure
JSON STRUCTURECloudsearch Define Index Field Request Structure
JSON STRUCTURECloudsearch Define Index Field Response Structure
JSON STRUCTURECloudsearch Delete Domain Response Structure
JSON STRUCTURECloudsearch Describe Domains Response Structure
JSON STRUCTURECloudsearch Describe Index Fields Response Structure
JSON STRUCTURECloudsearch Domain Status Structure
JSON STRUCTURECloudsearch Index Documents Response Structure
JSON STRUCTUREScroll within the panel for all 9 ·
Examples 9
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 9 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Website Search
Add powerful full-text search capabilities to websites and web applications.
E-Commerce Product Search
Enable customers to find products with faceted filtering and relevance ranking.
Document Search
Search across large document repositories with Boolean and proximity search.
Geospatial Search
Find resources by location with geospatial search queries.
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Amazon S3
Index documents stored in S3 buckets.
Amazon DynamoDB
Search DynamoDB data by exporting to CloudSearch.
AWS IAM
Control access to search domains with IAM policies.
Amazon CloudFront
Cache search results at CloudFront edge for lower latency.
Resources
Every other property we hold for Amazon CloudSearch — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/amazon-cloudsearch · machine-readable index on apis.io