AWS Cloud Map

Name: AWS Cloud Map API
Brand: AWS Cloud Map
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkingapiKey26 EndpointsREST

For Agents

Register and discover service instances dynamically across microservices using AWS Cloud Map. Agents can create namespaces, register instances, and resolve services via DiscoverInstances.

Quickstart

Get started with AWS Cloud Map in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"discover healthy service instances in aws cloud map"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with AWS Cloud Map API.

Create public, private DNS, or HTTP namespaces with CreateHttpNamespace, CreatePrivateDnsNamespace, CreatePublicDnsNamespace

Define services within a namespace and configure their DNS records or health-check behaviour

Resolve services at runtime with DiscoverInstances, optionally filtered by attributes and health

GET STARTED

Start building with AWS Cloud Map API

Explore with Jentic

View OpenAPI Document

Use for: I need to create a private DNS namespace for an internal microservice mesh, Register a new instance of a service so callers can discover it, Discover all healthy instances of a given service name, Update the custom health status of a registered instance

Not supported: Does not perform load balancing, service-mesh routing, or DNS hosting outside its managed namespaces — use for service registration and discovery only.

Jentic publishes the only available OpenAPI document for AWS Cloud Map, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AWS Cloud Map, keeping it validated and agent-ready. Cloud Map is the AWS service-discovery layer for microservices: it lets applications register service instances with a custom name, attach health checks, and resolve them via DNS or an HTTP API at runtime. Agents can create public or private DNS namespaces, define services with DNS or HTTP-only configurations, register and deregister instances, run DiscoverInstances queries, and inspect operation status. The 26 operations cover namespaces, services, instances, and discovery.

Use Cases

Patterns agents use AWS Cloud Map API for, with concrete tasks.

★ Service Discovery for Containerised Microservices

Teams running ECS, EKS, or hybrid workloads use Cloud Map as a runtime registry. Each service registers itself with attributes such as version and zone, callers use DiscoverInstances to resolve healthy targets, and Cloud Map returns up to eight matching records. Health checks on Route 53 or custom HealthCheckCustomConfig keep unhealthy instances out of results.

CreatePrivateDnsNamespace 'internal.local' on a VPC, CreateService 'orders' under it, RegisterInstance with InstanceId='orders-1' and Attributes containing IPv4 and PORT, then DiscoverInstances to confirm resolution.

Hybrid Service Registry with HTTP Namespaces

When clients cannot use DNS — for example, agents running outside the VPC — an HTTP-only namespace combined with DiscoverInstances replaces DNS resolution with an authenticated HTTP lookup. This lets non-AWS workloads register and discover services through the same Cloud Map control plane.

CreateHttpNamespace 'agents-mesh', CreateService inside it, RegisterInstance for an off-VPC worker, then DiscoverInstances filtered by HealthStatus=HEALTHY.

Operations and Drift Tracking

Long-running Cloud Map operations (namespace creation, service updates, deregistration) return an OperationId. Operators use GetOperation and ListOperations to track completion and detect failures, surfacing drift between intended and actual registry state.

Call ListOperations filtered by Status=PENDING, then GetOperation for each returned id to summarise which namespace or service operations are still in flight.

AI Agent Service Resolution via Jentic

AI agents using Jentic can resolve internal services on demand without holding AWS SDKs or DNS resolvers. The agent searches by intent, loads the DiscoverInstances schema, and executes against vault-stored AWS credentials to obtain healthy targets.

Search Jentic for 'discover service instances in cloud map', execute DiscoverInstances for NamespaceName='internal.local' and ServiceName='orders' with HealthStatus=HEALTHY, and return the resulting Instances array.

Key Endpoints

26 endpoints — jentic publishes the only available openapi specification for aws cloud map, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#X-Amz-Target=Route53AutoNaming_v20170314.CreatePrivateDnsNamespace

Create a private DNS namespace inside a VPC

POST

/#X-Amz-Target=Route53AutoNaming_v20170314.CreateHttpNamespace

Create an HTTP-only namespace for service discovery

POST

/#X-Amz-Target=Route53AutoNaming_v20170314.CreateService

Define a service within a namespace

POST

/#X-Amz-Target=Route53AutoNaming_v20170314.RegisterInstance

POST

/#X-Amz-Target=Route53AutoNaming_v20170314.DiscoverInstances

Resolve healthy instances for a service

POST

/#X-Amz-Target=Route53AutoNaming_v20170314.DeregisterInstance

Remove an instance from a service

POST

/#X-Amz-Target=Route53AutoNaming_v20170314.GetOperation

Inspect an async operation by id

POST

/#X-Amz-Target=Route53AutoNaming_v20170314.CreatePrivateDnsNamespace

Create a private DNS namespace inside a VPC

POST

/#X-Amz-Target=Route53AutoNaming_v20170314.CreateHttpNamespace

Create an HTTP-only namespace for service discovery

POST

/#X-Amz-Target=Route53AutoNaming_v20170314.CreateService

Define a service within a namespace

POST

/#X-Amz-Target=Route53AutoNaming_v20170314.RegisterInstance

POST

/#X-Amz-Target=Route53AutoNaming_v20170314.DiscoverInstances

Resolve healthy instances for a service

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS access keys are stored encrypted in the Jentic vault. Cloud Map calls are signed with SigV4 inside Jentic, so the raw credential never appears in the agent's prompt or runtime.

Intent-based discovery

Agents search by intent (for example, 'discover service instances' or 'register an instance') and Jentic returns the matching Cloud Map operations with parameter schemas, letting the agent invoke DiscoverInstances or RegisterInstance directly.

Time to first call

Direct Cloud Map integration: 1-2 days to wire up SigV4 signing, JSON-RPC style x-amz-target headers, and operation polling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Amazon Route 53

DNS hosting that backs Cloud Map's public and private DNS namespaces

Use Route 53 directly for static DNS records; use Cloud Map when the records change dynamically with service registration

Complementary

AWS App Mesh

Service mesh that integrates with Cloud Map for service-to-service routing

Combine App Mesh routing with Cloud Map registration when fine-grained traffic policies are needed alongside discovery

Alternative

Amazon EKS

Kubernetes-native service discovery via the Kubernetes API; an alternative to Cloud Map inside a single cluster

Use Kubernetes Services inside an EKS cluster; reach for Cloud Map when discovery must span clusters or non-Kubernetes workloads

FAQs

Specific to using AWS Cloud Map API through Jentic.

Why is there no official OpenAPI spec for AWS Cloud Map?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Cloud Map via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the AWS Cloud Map use?

Cloud Map uses AWS Signature Version 4 with IAM credentials and permissions on the servicediscovery:* actions. Through Jentic, the AWS access key and secret are stored encrypted in the vault and SigV4 signing happens server-side — the agent never handles the raw credential.

Can I discover services without using DNS?

Yes. HTTP-only namespaces and the DiscoverInstances API let clients resolve services over HTTPS without a DNS resolver. This is the recommended path for clients outside the namespace's VPC or for agents that cannot perform DNS lookups.

What are the rate limits for the AWS Cloud Map?

Cloud Map applies standard AWS throttling — control-plane operations like CreateService are limited to a few requests per second per account, while DiscoverInstances supports higher throughput suited for runtime resolution. Throttled calls return a ThrottlingException; retry with exponential backoff.

How do I register a service instance through Jentic?

Through Jentic, search for 'register a service instance in cloud map', load the RegisterInstance schema, and execute with ServiceId, InstanceId, and the Attributes map (typically AWS_INSTANCE_IPV4 and AWS_INSTANCE_PORT). Jentic returns the OperationId so the agent can poll completion via GetOperation.

Is AWS Cloud Map free?

Cloud Map charges per registered service per month and per million DiscoverInstances API calls. Health checks billed by Route 53 apply when DNS-based health checking is enabled; see https://aws.amazon.com/cloud-map/pricing/ for the current rates.