Amazon ECS Service Connect adds support for cross-account workloads
Amazon ECS Service Connect now supports seamless communication between services residing in different Amazon Web Services accounts through integration with Amazon Resource Access Manager (Amazon RAM). This enhancement simplifies resource sharing, reduces duplication, and promotes consistent service-to-service communication across environments for organizations with multi-account architectures.
Amazon ECS Service Connect leverages Amazon Cloud Map namespaces for storing information about ECS services and tasks. To enable seamless cross-account communication between Amazon ECS Service Connect services, you can now share the underlying Amazon Cloud Map namespaces using Amazon RAM with individual Amazon Web Services 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 use the same namespace to register Amazon ECS Service Connect services residing in multiple Amazon Web Services accounts, simplifying service discovery and connectivity. Application developers can then build services that rely on a consistent, shared registry without worrying about availability or synchronization across accounts. Cross-account connectivity support improves operational efficiency and makes it easier to scale Amazon ECS workloads as your organization grows by reducing duplication and streamlining access to common services.
This feature is available now with both EC2 and Fargate launch modes in the Amazon Web Services China (Beijing) Region, operated by Sinnet, and Amazon Web Services China (Ningxia) Region, operated by NWCD, via the Amazon Web Services Management Console, API, SDK, CLI, and CloudFormation. To learn more, please refer to the Amazon ECS Service Connect documentation.