Recommendations to others considering AWS Cloud Map:
There's no need to rewrite another service discovery module. Just register your microservices and any important information with CloudMap and use that in your orchestration layer. Review collected by and hosted on G2.com.
What problems is AWS Cloud Map solving and how is that benefiting you?
The primary use case I have is service discovery. I can use it at an orchestration layer for how to contact my microservices without having to pass in static values on startup to a container or pass in environment variables to a serverless function.
I have also used it for tracking business events. When you don't fire things off using something like SNS, it's good to keep a business event repository for your application. CloudMap works perfectly for tracking things across microservices like that. Review collected by and hosted on G2.com.