# AWS Cloud Map

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/aws-cloud-map

> AWS Cloud Map is a cloud resource discovery service that allows developers to define custom names for their application resources, and it keeps track of the changing locations of these dynamically changing resources, making it easier to discover and connect to them in a cloud environment.

Practice exams covering AWS Cloud Map: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty).

## 6 key features of AWS Cloud Map

AWS Cloud Map offers automatic service discovery, customizable naming for resources, health status monitoring, seamless integration with AWS services, and facilitates application recovery by rerouting traffic to healthy endpoints.

1. **Service Discovery**: AWS Cloud Map supports automatic service discovery, which helps applications discover and connect to services running in any infrastructure â AWS Cloud, on-premises, or other cloud platforms â without hard coding IP addresses or ports.
2. **Customizable Naming for Resources**: With AWS Cloud Map, you can define custom names for your application resources, such as Amazon ECS services, Amazon EC2 instances, or any other cloud resource, thereby making it easier to manage and access them.
3. **Health Status Monitoring**: When health checking is configured for a service, AWS Cloud Map returns only healthy instances during discovery.
4. **Integration with AWS Services**: Amazon ECS registers tasks in AWS Cloud Map when service discovery is enabled. For Amazon EKS, the Cloud Map provider in ExternalDNS propagates service locations to the registry as services launch and removes them on termination.
5. **Application Recovery**: Facilitates rapid application recovery by helping applications discover healthy endpoints, thus improving your application's availability and reliability with minimal intervention.
6. **Service-Level Attributes**: Use UpdateServiceAttributes to store custom metadata at the service level, avoiding duplication across instances and allowing updates without changing instance attributes.

## Where AWS Cloud Map is used

AWS Cloud Map is utilized for seamless service discovery in microservices architectures, easing application migrations to the cloud through service registry, enabling dynamic load balancing by health status, and ensuring high availability with health check monitoring.

1. **Service Discovery for Microservices**: AWS Cloud Map facilitates the discovery of microservices, enabling applications to quickly locate and communicate with various service instances. Through customizable naming for resources, applications can easily resolve the locations of microservices without hard-coding IP addresses or port numbers, thus simplifying service intercommunication and scaling.
2. **Application Migration to the Cloud**: Organizations migrating applications to the cloud can leverage AWS Cloud Map to streamline the process. By abstracting the underlying cloud resources and providing a service registry, Cloud Map allows for easy registration and discovery of both on-premises and cloud-based components, reducing the complexity of hybrid or multi-cloud architectures.
3. **Dynamic Load Balancing**: With AWS Cloud Map, applications can implement dynamic load balancing by querying the service directory for the health status of service instances. By directing traffic to healthy instances based on real-time health checks, Cloud Map enhances application availability and performance without the need for a separate load balancer.
4. **Health Check Monitoring**: When health checking is configured for a service, AWS Cloud Map returns only healthy instances, helping applications avoid unhealthy resources during discovery.

## How AWS Cloud Map is priced

AWS Cloud Map pricing includes request-based charges for each service discovery and namespace request, and resource-based pricing for configured health checks.

- **Request-Based Usage**: AWS Cloud Map charges per million DiscoverInstances API calls and per million DiscoverInstancesRevision API calls.
- **Resource-Based Pricing**: AWS Cloud Map charges per registered resource per month; resources registered through Amazon ECS Service Discovery are exempt from the service registry charge.
- **Optional Amazon Route 53 Charges**: Enabling DNS-based discovery or Amazon Route 53 health checks for IP-addressed resources incurs additional Amazon Route 53 DNS and health check usage charges.

## Services AWS Cloud Map works with

- **[Amazon API Gateway](https://blowstack.com/tools/cloud-services-hub/amazon-api-gateway)**: AWS Cloud Map provides service discovery for API Gateway HTTP API private integrations. API Gateway discovers healthy backend instances registered in a Cloud Map service and routes requests to their IP addresses and ports.
- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: DNS queries for AWS Cloud Map namespaces can be logged through Route 53 to CloudWatch Logs. These logs help troubleshoot DNS-based discovery of resources registered in Cloud Map.
- **[Amazon DynamoDB](https://blowstack.com/tools/cloud-services-hub/amazon-dynamodb)**: AWS Cloud Map can register DynamoDB tables as discoverable resources, storing their identifying information in custom attributes. Applications can discover the table associated with a logical service name rather than hard-coding its name.
- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: AWS Cloud Map can register EC2 instances and expose their addresses through DNS or API-based discovery. Registration can use an EC2 instance ID to obtain the instance's primary private IPv4 address.
- **[Amazon Elastic Container Service (Amazon ECS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-service-(amazon-ecs))**: AWS Cloud Map integrates with ECS service discovery to register and deregister tasks as they start and stop. ECS Service Connect also uses Cloud Map namespaces to organize and discover services.
- **[Amazon Elastic Kubernetes Service (Amazon EKS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-kubernetes-service-(amazon-eks))**: AWS Cloud Map integrates with EKS through the Kubernetes ExternalDNS connector. The connector maintains Cloud Map discovery records for Kubernetes services as their endpoints change.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: AWS Cloud Map API activity recorded by CloudTrail can be matched by EventBridge rules. For example, a rule can trigger an automation workflow when a Cloud Map namespace or service is deleted.
- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: AWS Cloud Map creates Route 53 hosted zones and DNS records for DNS-based namespaces and registered service instances. It can also create Route 53 health checks to exclude unhealthy endpoints from DNS discovery.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: AWS Cloud Map can register S3 buckets as discoverable resources using custom attributes that identify the bucket. Applications can retrieve the bucket associated with a logical service name through API-based discovery.
- **[Amazon Simple Queue Service (Amazon SQS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-queue-service-(amazon-sqs))**: AWS Cloud Map can register SQS queues with custom attributes containing their identifying information, such as a queue URL. Applications can discover the queue assigned to a logical service without embedding its location in configuration.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: AWS Cloud Map associates private DNS namespaces with a VPC, creating a private Route 53 hosted zone for service discovery. Resources in the VPC can resolve registered service names to private endpoint addresses.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: AWS Cloud Map namespaces, services, and service instances can be provisioned with CloudFormation resource types. This lets application infrastructure and its discovery configuration be created, updated, and deleted together.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: AWS Cloud Map integrates with CloudTrail to record supported API activity, including namespace, service, and instance management operations. These records identify who made a request, when it occurred, and the request parameters.
- **[AWS Fargate](https://blowstack.com/tools/cloud-services-hub/aws-fargate)**: AWS Cloud Map supports discovery of ECS services running on Fargate. ECS registers the tasks' private IP addresses and ports so other services can locate them without tracking individual task replacements.
- **[AWS Lambda](https://blowstack.com/tools/cloud-services-hub/aws-lambda)**: AWS Cloud Map can represent Lambda functions as discoverable resources by storing function identifiers in service-instance custom attributes. Applications can discover the function associated with a logical service name before invoking it.
- **[AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink)**: AWS Cloud Map supports interface VPC endpoints through PrivateLink. Applications can access supported Cloud Map management and discovery APIs privately without an internet gateway or NAT device.
- **[AWS Resource Access Manager (AWS RAM)](https://blowstack.com/tools/cloud-services-hub/aws-resource-access-manager-(aws-ram))**: AWS Cloud Map namespaces can be shared with other AWS accounts through AWS RAM. This allows services in different accounts, including ECS Service Connect services, to participate in a shared discovery namespace.
- **[AWS Resource Groups and Tag Editor](https://blowstack.com/tools/cloud-services-hub/aws-resource-groups-and-tag-editor)**: AWS Cloud Map namespaces and services support tags that can be used with Resource Groups and Tag Editor. This helps organize discovery resources by application or environment and manage their tags centrally.
- **[AWS Step Functions](https://blowstack.com/tools/cloud-services-hub/aws-step-functions)**: AWS Cloud Map APIs can be called from Step Functions workflows through AWS SDK integrations. A workflow can register a newly deployed endpoint, update its custom health status, and deregister it during teardown.
- **[Elastic Load Balancing (ELB)](https://blowstack.com/tools/cloud-services-hub/elastic-load-balancing-(elb))**: AWS Cloud Map can create Route 53 alias records that point to an Elastic Load Balancing load balancer. Clients can then use a Cloud Map service name to reach the load-balanced application.

## What is AWS Cloud Map

AWS Cloud Map is an advanced cloud-based service designed and offered by Amazon Web Services that significantly simplifies the process of resource discovery within the cloud ecosystem. This service facilitates the automatic registration and discovery of application resources, such as microservices, IP addresses, databases, and queues, across your AWS environment. By providing a detailed registry of application services, AWS Cloud Map enables applications to discover and connect with each other through dynamic, cloud-native discovery mechanisms.

The core functionality of AWS Cloud Map revolves around its service registry that maintains a comprehensive and up-to-date map of the technical landscape of application services. This service does not merely record service instances; it also tracks their metadata, such as version numbers, endpoints, and other critical operational parameters. Thus, it eases the management and configuration of containerized microservices, serverless applications, and traditional workloads by automating service discovery. This automation is key to maintaining high availability and scalability within dynamic cloud environments where services frequently change due to scaling operations or updates.

Health checking is configured at the service level, where you can choose whether to check resource health and whether to use Amazon Route 53 health checks or a third-party health checker.

A service can have at most 1,000 registered instances in a Region; this quota is not adjustable.

One of the hallmark features of AWS Cloud Map is its seamless integration with other AWS services. For instance, it works closely with Amazon ECS and Amazon EKS to integrate service discovery into the application deployment and management lifecycle. By leveraging AWS Cloud Map, developers can abstract away the complexity of service interconnectivity, focusing instead on building and scaling their applications.

AWS Cloud Map prioritizes ease of use and flexibility. It allows developers to define custom names for their application resources, making it simpler to manage and locate services across the cloud environment. Through its API, AWS Cloud Map enables programmatic registration and deregistration of services, and it supports both HTTP and DNS queries for service discovery. This dual support ensures that applications can efficiently discover their dependencies regardless of their architecture or communication protocol.

A namespace groups services for an application and determines how resources are discovered: through the DiscoverInstances API, DNS queries within a VPC, or public DNS queries.

DiscoverInstances requests are throttled per AWS account and Region. Exceeding an API throttling quota returns RequestLimitExceeded.

If MaxResults is omitted from a DiscoverInstances request, AWS Cloud Map returns up to 100 instances.

In a highly dynamic and scale-driven cloud ecosystem, AWS Cloud Map stands out by providing critical real-time service discovery capabilities, which are essential for achieving operational excellence and automation. It significantly contributes to reducing the overhead associated with manual configuration and updates, leading to faster deployment cycles and a more resilient infrastructure. Furthermore, by centralizing service registration and discovery, AWS Cloud Map enhances the visibility and governance of distributed application resources, allowing organizations to maintain control over their complex cloud environments.

In conclusion, AWS Cloud Map is a powerful, flexible service discovery solution that streamlines the operation of cloud-native applications by automating the discovery of application components. Its integration with other AWS services and its support for custom service naming and programmatic interactions make it an invaluable tool for developers looking to enhance the scalability, reliability, and efficiency of their cloud-based applications.
