Amazon Cloud Map
Amazon Cloud Map is a cloud resource discovery service that maintains an updated registry of application resources and their locations. Define custom names for application resources and use Cloud Map to dynamically discover service dependencies with integrated health checking and automatic updates.
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 Cloud Map the way a machine reads it — 64 machine-readable artifacts across 3 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 Cloud Map scores 59.2/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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 Cloud Map
Each block below is one kind of artifact we hold for Amazon Cloud Map. 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 3
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 Cloud Map Instances API
Operations for registering and discovering service instances
Amazon Cloud Map Namespaces API
Operations for managing service discovery namespaces
Amazon Cloud Map Services API
Operations for managing services within namespaces
Features 5
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.
Service Registry
Maintain an up-to-date registry of application resources with custom naming.
Health Monitoring
Continuously monitor health of every IP-based component and route only to healthy endpoints.
Dynamic Discovery
Automatically update service registries as services scale up or down.
Custom Names
Define custom names for application resources rather than hardcoding IP addresses.
Multi-Environment Support
Maintain service registries across different deployment environments, regions, and application versions.
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 Cloud Map 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 Cloud Map API Rules
SPECTRALAmazon Cloud Map API Rules
SPECTRALJSON Schema 13
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.
CreateServiceRequest
JSON SCHEMACreateServiceResponse
JSON SCHEMADiscoverInstancesRequest
JSON SCHEMADiscoverInstancesResponse
JSON SCHEMAHttpInstanceSummary
JSON SCHEMAInstance
JSON SCHEMAListInstancesResponse
JSON SCHEMAListNamespacesResponse
JSON SCHEMAListServicesResponse
JSON SCHEMANamespace
JSON SCHEMARegisterInstanceRequest
JSON SCHEMARegisterInstanceResponse
JSON SCHEMAService
JSON SCHEMAScroll within the panel for all 13 ·
JSON Structure 13
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.
Cloud Map Create Service Request Structure
JSON STRUCTURECloud Map Create Service Response Structure
JSON STRUCTURECloud Map Discover Instances Request Structure
JSON STRUCTURECloud Map Discover Instances Response Structure
JSON STRUCTURECloud Map Http Instance Summary Structure
JSON STRUCTURECloud Map Instance Structure
JSON STRUCTURECloud Map List Instances Response Structure
JSON STRUCTURECloud Map List Namespaces Response Structure
JSON STRUCTURECloud Map List Services Response Structure
JSON STRUCTURECloud Map Namespace Structure
JSON STRUCTURECloud Map Register Instance Request Structure
JSON STRUCTURECloud Map Register Instance Response Structure
JSON STRUCTURECloud Map Service Structure
JSON STRUCTUREScroll within the panel for all 13 ·
Examples 13
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.
Cloud Map Instance Example
EXAMPLECloud Map Namespace Example
EXAMPLECloud Map Service Example
EXAMPLEScroll within the panel for all 13 ·
Security Posture 4
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.
Microservice Discovery
Enable services to locate dependencies in dynamic container environments with ECS and EKS.
Health-Based Routing
Ensure traffic routes only to verified healthy service endpoints.
CI/CD Integration
Automatically register and deregister services during CI/CD pipeline deployments.
Multi-Region Service Mesh
Discover services across multiple AWS regions with a unified namespace.
Integrations 5
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 ECS
Automatically register ECS task IPs in Cloud Map as containers launch.
Amazon EKS
Integrate Kubernetes service discovery with Cloud Map for hybrid environments.
Amazon Route 53
DNS-based service discovery backed by Route 53 private hosted zones.
AWS App Mesh
Use Cloud Map as the service registry for App Mesh virtual services.
AWS IAM
Control access to Cloud Map namespaces with IAM policies.
Resources
Every other property we hold for Amazon Cloud Map — 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-cloud-map · machine-readable index on apis.io