AWS Cloud Map cost: per registered resource and per lookup

Quick answer

Cloud Map bills per registered resource per month (each service instance in the registry) and per discovery API call (DiscoverInstances lookups), plus any Route 53 health checks it uses. It is inexpensive, but very high-frequency discovery lookups from many clients can accumulate, so caching discovery results and using DNS-based discovery where appropriate are the levers.

AWS Cloud Map is a service-discovery registry: services register their instances, and clients look them up to find healthy endpoints. Its pricing is per registered resource and per lookup, both small, so for most architectures it is a minor cost, but lookup-heavy patterns can add up.

Registered resources and lookups

Dimension	Bills for
Registered resources	Per resource in the registry per month
Discovery API calls	Per DiscoverInstances lookup
Health checks	Route 53 health check charges (if used)

You pay a small monthly charge per registered resource (each service instance) and per API discovery call. If you configure health checking, the underlying Route 53 health checks bill separately. For a modest service catalog with reasonable lookup rates, the total is small.

Where lookups add up

The cost that grows is discovery API calls: if every client looks up a service on every request rather than caching the result, a high-traffic system generates enormous lookup volume. Caching discovery results for a sensible interval, or using Cloud Map's DNS-based discovery (which leans on resolver caching), sharply reduces API-call volume.

Controlling Cloud Map cost

Cache discovery results in clients rather than looking up on every request, use DNS-based discovery where it fits so resolver caching absorbs lookups, keep the registry to actual services, and manage health checks. For most architectures Cloud Map is inexpensive; the lever, when it matters, is not looking up on every request, the same caching principle as reducing Route 53 query cost.

FAQ

How is AWS Cloud Map priced?

Per registered resource per month (each service instance in the registry) and per discovery API call (DiscoverInstances lookups), plus any Route 53 health checks it uses if you configure health checking. Both core charges are small, so for most architectures Cloud Map is a minor cost.

What drives Cloud Map cost?

Discovery API calls, when clients look up services frequently. If every client looks up a service on every request rather than caching, a high-traffic system generates large lookup volume. The per-registered-resource charge is small, so lookup frequency is the main variable that can grow.

How do I reduce Cloud Map cost?

Cache discovery results in clients for a sensible interval rather than looking up on every request, use Cloud Map's DNS-based discovery where it fits so resolver caching absorbs lookups, keep the registry to actual services, and manage health checks. Not looking up on every request is the main lever.

Does Cloud Map charge for health checks?

If you configure health checking, the underlying Route 53 health checks bill separately at their standard rate. The Cloud Map charges themselves are for registered resources and discovery API calls; health checks add the Route 53 health-check cost on top when enabled.

Is Cloud Map expensive?

For most architectures, no. The per-registered-resource and per-lookup charges are small, so a modest service catalog with reasonable lookup rates costs little. It only grows notably when clients perform high-frequency discovery lookups without caching, which caching or DNS-based discovery addresses.

Does C3X estimate Cloud Map cost?

Cloud Map cost is driven by registered resources and discovery lookups, which are usage inputs. C3X prices the surrounding infrastructure, and you model your service count and lookup volume to estimate the service-discovery charges.

What to do next

Estimate the infrastructure around your service discovery before you deploy. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.