Amazon Cloud Map adds support for cross-account service discovery

Amazon Cloud Map adds support for cross-account service discovery

Amazon Cloud Map now supports cross-account service discovery through integration with Amazon Resource Access Manager (Amazon RAM). This enhancement lets you seamlessly manage and discover cloud resources—such as Amazon ECS tasks, Amazon EC2 instances, and Amazon DynamoDB tables—across Amazon accounts. By sharing your Amazon Cloud Map namespace via Amazon RAM, workloads in other accounts can discover and manage resources registered in that namespace. This enhancement simplifies resource sharing, reduces duplication, and promotes consistent service discovery across environments for organizations with multi-account architectures.

You can now share your Amazon Cloud Map namespaces using Amazon RAM with individual Amazon accounts, specific Organizational Units (OUs), or your entire Amazon Organization. To get started, create a resource share in Amazon RAM, add the namespaces you want to share, and specify the principals (accounts, OUs, or the organization) that should have access. This enables platform engineers to maintain a centralized service registry—or a small set of registries—and share them across multiple accounts, simplifying service discovery. Application developers can then build services that rely on a consistent, shared registry without worrying about availability or synchronization across accounts. Amazon Cloud Map’s cross-account service discovery support improves operational efficiency and makes it easier to scale service discovery as your organization grows by reducing duplication and streamlining access to namespaces.

This feature is available now in all commercial AWS Regions via the Amazon Management Console, API, SDK, CLI, and CloudFormation. To learn more, please refer to the Amazon Cloud Map documentation.

Categories:

Source: Amazon Web Services



Latest Posts

Pass It On
Leave a Comment

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *