AWS Cloud Map Reviews & Product Details

What I like best is how quietly it takes the “where do I even reach that service?” headache away.

In my day-to-day I just give every micro-service a name—something plain like “user-profile” or “order-validator”—and Cloud Map keeps the latest IP/port, health status, and even a few custom attributes in one tiny record. After that, no matter how many times auto-scaling spins nodes up or down, the rest of the fleet finds them automatically. I stopped hard-coding IPs in config files, stopped juggling Route 53 entries by hand, and never had to tell the front-end team “wait, the endpoint changed again.” It feels like the service directory just looks after itself, so I can stay in the code instead of babysitting DNS. Review collected by and hosted on G2.com.

What still trips me up is how “split-brained” Cloud Map feels inside the AWS console. Half the controls are in Cloud Map itself, but the moment I want to attach a namespace to an ECS service or an EKS ingress, I’m suddenly clicking through three other services (ECS, EKS, App Mesh, even Route 53) just to view what are essentially the same records.

Debugging is the worst part. I’ll notice an instance that looks unhealthy in Cloud Map, but to figure out why I have to bounce over to ECS tasks, then into CloudWatch logs, and then back to Cloud Map to deregister the bad node. It ends up feeling like the service directory is supposed to be the single source of truth—except when it isn’t, and I’m still stuck hunting across tabs to piece everything together. Review collected by and hosted on G2.com.

The best thing about AWS Cloud Map is its ability to simplify service discovery in a dynamic cloud environment. With custom names for services and dynamic updates, applications can easily locate and connect to the resources they need. The integration with Amazon Route 53 enables seamless DNS resolution, while multi-region support ensures global scalability. With a comprehensive API and SDK, Cloud Map empowers developers to programmatically manage service discovery. Overall, Cloud Map streamlines infrastructure management enhances application resilience, and accelerates development in cloud-based architectures. Review collected by and hosted on G2.com.

There are a few potential dislikes when it comes to AWS Cloud Map. Firstly, there can be a learning curve associated with understanding and implementing service discovery concepts. Secondly, the pricing structure of Cloud Map, like other AWS services, can be complex, and it's important to carefully manage costs to avoid unexpected expenses. Additionally, while Cloud Map offers basic service discovery functionality, it may not provide advanced features or extensive customization options compared to more specialized service discovery solutions. Lastly, as with any cloud-based service, there is always a level of dependency on the underlying infrastructure, which can occasionally introduce issues or limitations. Review collected by and hosted on G2.com.

The first part is we can separate our services based on our application infrastructure with namespaces. In AWS Cloud Map the namespaces really help us to group our application infrastructures.

The next thing is all the services that are registered within a namespace will easily communicate with each other and also they can easily be discoverable within the namespace.

These two things are helping us with our little usage of AWS Cloud Map... Review collected by and hosted on G2.com.

From my perspective, I think it incurs costs a little higher. And this service has certain limitations regarding the number of services and instances that can be registered within a namespace. Lastly, setting up and managing AWS Cloud Map requires familiarity with service discovery concepts and AWS services like Little Complexity. Review collected by and hosted on G2.com.

Since we have a global business, It is highly beneficial to us that AWS cloud map allows Multi-region support, allowing other services to discover and communicate with us. Review collected by and hosted on G2.com.

There was an initial learning curve to it since it added extra components to the mix, but once it was cemented with the team - there has been no issue. Maybe a more infographic section on learning would be appreciated, or a knowledge repository for the initial days. Review collected by and hosted on G2.com.

I have a microservice application running on EKS. There are multiple services running on different pods. I needed to discover the available services. I used Cloudmap which enabled me to dynamically discover available services and I can additionally perform health checks on each service endpoint.

Best thing about AWS Cloudmap is flexibility and easy to use solution for cloud management. Review collected by and hosted on G2.com.

The things that are not good in AWS Cloud Map is the cost of running as it depends on how many services are registered with it. And since it is relatively new hence we have limited community support for it. Review collected by and hosted on G2.com.

I believe that the registry and discovery features of AWS Cloud Map enable you to manage your cloud resources more effectively. The App Mesh, on the other hand, is a service mesh that enables you to more effectively monitor networking between services that transcend computational architecture. It works well and is simple to use. Having one of the best user experiences is made possible with a user-friendly app. An excellent programme that is simple to use, effective, and efficient. The fact that we can register any kind of application, including a database or an API endpoint, is the nicest feature. By continually examining whether the location is current, it also helps in the detection of downtimes. Additionally, the discovery option is best suited for improved cloud resource management. Review collected by and hosted on G2.com.

The architecture of the programme needs to be watched since if it uses more resources than expected, the billing may suffer. Initial configuration can be a little tough and complex, thus it's important to have solid background knowledge. The tool is referred to as AWS Cloud Map. It is a little bit chaotic and does not offer mapping features like CloudMapper. renamed "Amazon Route 53 Auto Naming" Review collected by and hosted on G2.com.

It's very wonderful experience with AWS cloud map.. with that we can easily monitor the services and health check of your services..it is fully managed services. Review collected by and hosted on G2.com.

Nothing to like the AWs service because my experience it is very good to you use n satisfied with the use. So my experience nothing to dislike the AWs cloud map. Review collected by and hosted on G2.com.

* Grouping resources based on namespace and ease of management.

* Resource lookup is efficient and has multi-region support.

* Resource heart-beat check support and notifies of down time. Review collected by and hosted on G2.com.

* Bit complex to understand and implement.

* Could have provided a good video example of setup, which can be helpful for anyone to adopt quickly. Review collected by and hosted on G2.com.

The best help i got in my work is i teracting woth mysql objects and functions. It also constantly take care of rhe healrh of the resourse which is good help in our management sustem Review collected by and hosted on G2.com.

Nothing much as of now . It all seems to be working fine. Soon will be interacting more and then if face any error i will definitely raise a query based on that thankyou . Review collected by and hosted on G2.com.

Its cost effective no need costly server specially for small startups. It's more flexible and scalable. Review collected by and hosted on G2.com.

Internet connection and if need extra storage it will increase cost.

Main concern about security and privacy. Review collected by and hosted on G2.com.