G2

Atharva P.

Cloud BI Engineer

Enterprise (> 1000 emp.)

7/24/2026

"Seamless, Secure Resource Sharing Across AWS Accounts with AWS RAM"

4/5

What do you like best about AWS Resource Access Manager (RAM)?

What I like most about AWS Resource Access Manager (AWS RAM) is how easy it makes sharing AWS resources across multiple AWS accounts and Organizational Units. Rather than duplicating infrastructure like subnets, Transit Gateways, Route 53 Resolver rules, or License Manager configurations, I can share those resources securely while still keeping them centrally managed.

I also appreciate its native integration with AWS Organizations, which makes resource sharing in an enterprise feel seamless and straightforward, without the need for complex networking setups or lots of manual configuration. Review collected by and hosted on G2.com.

What do you dislike about AWS Resource Access Manager (RAM)?

AWS RAM only supports sharing certain AWS resource types, so not every AWS service can take advantage of it. It can also take some upfront learning to understand which resources are shareable and how ownership, permissions, and account associations work in practice. Review collected by and hosted on G2.com.

What problems is AWS Resource Access Manager (RAM) solving and how is that benefiting you?

AWS RAM helps solve the challenge of managing duplicate infrastructure across multiple AWS accounts.

For example, our networking team centrally managed Transit Gateways, shared VPC subnets, and Route 53 Resolver rules with application accounts using AWS RAM. Rather than provisioning the same networking resources in every account, application teams consumed these centrally managed resources while ownership and control stayed with the networking account.

As a result, we reduced infrastructure duplication, simplified governance, and lowered operational overhead. Review collected by and hosted on G2.com.