Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request
Services running with ECS Service Connect can communicate cross account without the overhead of building complex organization-wide DNS rules and IAM roles in order to communicate with different AWS accounts within their organization.

Which service(s) is this request for?
ECS Service Connect

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?

Are you currently working around this issue?
Researching

Additional context
Anything else we should know?

Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)