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.
Amazon Cloud Map publishes 3 APIs on the APIs.io network: Instances API, Namespaces API, and Services API. Tagged areas include Cloud Map, Service Discovery, Microservices, and DNS.
The Amazon Cloud Map catalog on APIs.io includes 1 JSON-LD context and 2 Spectral governance rulesets.
Amazon Cloud Map’s developer surface includes authentication, developer portal, documentation, support, engineering blog, developer console, signup flow, and 22 more developer resources.
Kin Score
APIs 3
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
Open Collections 4
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONAmazon Cloud Map Instances API
OPEN COLLECTIONAmazon Cloud Map Instances Namespaces API
OPEN COLLECTIONAmazon Cloud Map Instances Services API
OPEN COLLECTIONMCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
Amazon Cloud Map MCP Server
MCP SERVERFeatures 5
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 and semantic vocabularies used across these APIs.
Amazon Cloud Map Context
JSON-LDSpectral Rules 2
Spectral governance rulesets for linting and validating these APIs.
Amazon Cloud Map API Rules
SPECTRALAmazon Cloud Map API Rules
SPECTRALJSON Schema 13
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 for all 13
JSON Structure 13
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 for all 13
Examples 13
Example request and response payloads for these APIs.
Cloud Map Instance Example
EXAMPLECloud Map Namespace Example
EXAMPLECloud Map Service Example
EXAMPLEScroll for all 13
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
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 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
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
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
Other 1
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for providers
9 MCP tools reach this
find_providersBrowse and filter every provider in the catalog.get_provider_artifactsEvery artifact this provider publishes, grouped by type.get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.get_provider_toolsEvery MCP tool they ship, with the operation each wraps.get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.get_provider_ratingPRO — composite, band, trend and facet scores.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/providers/amazon-cloud-map"
curl "https://apis.io/api/v1/providers?limit=25"
curl "https://apis.io/api/v1/providers/amazon-cloud-map/operations?limit=25"
curl "https://apis.io/api/v1/providers/amazon-cloud-map/evidence"
Discovery needs no key. Ratings and market analysis are Pro.