AWSResourceAccessManagerFullAccess
Summary
Provides full access to AWS Resource Access Manager (AWS RAM). The AWS RAM User Guide says it provides full administrative access to view or modify the resource shares owned by your AWS account.
Permissions imported from the AWS Managed Policy Reference Guide; other sections reviewed against the listed AWS sources.
Identity
- ARN
arn:aws:iam::aws:policy/AWSResourceAccessManagerFullAccess- Default version
- v1
- Created
- Last edited
- Services
- ram
Control-plane actions (39)
By access level: 9 List, 3 Permissions management, 7 Read, 2 Tagging, 18 Write.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| Resource Access Manager | All 39 actions (see the Resource Access Manager page) | 9 List, 3 Permissions management, 7 Read, 2 Tagging, 18 Write; 0 restricted, 0 conditional | ram:* |
Data-plane actions (0)
By access level: none.
This policy grants no actions in this plane.
Excluded and conditional actions
No patterns are excluded by NotAction or Deny statements.
Resource scope and attachment
Resource scope across granted actions: all-resources.
Can be attached: Yes, to users, groups and roles.
Why this tier
- Grants at least 80% of the write and permissions-management actions of: ram (21 of 21).
Guidance
Practical scope
One statement allows ram:* on Resource "*", with no Condition. The AWS RAM User Guide describes it as granting permission to run any ram operations.
Use cases
- View or modify any information about the resource shares that are owned by your AWS account.
Best practices
- AWS managed policies don't grant least privilege permissions. The IAM User Guide suggests using IAM Access Analyzer to see which permissions principals actually use, then writing a custom policy or generating one with only the required permissions.
Security considerations
- ram:* allows every AWS RAM action on all resources. The AWS RAM User Guide says the policy lets principals view or modify any information about the resource shares owned by the account.
- You cannot change the permissions in an AWS managed policy. If AWS updates the policy, the update affects every user, group and role it is attached to.
Assignment guidance
You can attach this policy to your users, groups and roles. The reference page also links to guidance on creating a permission set using AWS managed policies in IAM Identity Center. It fits where full AWS RAM access is intended. Where a narrower scope is needed, AWS recommends customer managed policies specific to your use cases.
Related policies
Same service
- AmazonDataZoneGlueManageAccessRolePolicy
- AmazonDataZoneProjectRolePermissionsBoundary
- AmazonDataZoneSageMakerManageAccessRolePolicy
- AWSLakeFormationCrossAccountManager
- AWSLicenseManagerMasterAccountRolePolicy
- AWSLicenseManagerMemberAccountRolePolicy
- AWSMarketplaceResaleAuthorizationServiceRolePolicy
- AWSMarketplaceSubsidiaryAuthorizationServiceRolePolicy
Same domain
Frequently asked questions
- When should I attach AWSResourceAccessManagerFullAccess?
- The AWS RAM User Guide says you can attach it to your IAM identities and that it provides full administrative access to view or modify the resource shares owned by your AWS account. Attach it where that scope is intended. If someone needs less, AWS recommends customer managed policies specific to your use cases.
- What does AWSResourceAccessManagerFullAccess grant?
- It allows ram:* on all resources, which the AWS RAM User Guide describes as permission to run any ram operations on the resource shares owned by the account.
- What are the security risks of AWSResourceAccessManagerFullAccess?
- ram:* allows every AWS RAM action on all resources and the policy has no condition. AWS managed policies do not grant least privilege permissions, and an AWS update to the policy affects every identity it is attached to.
Policy JSON
{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"ram:*"
],
"Effect": "Allow",
"Resource": "*"
}
]
}
Version history
Current version v1, edited by AWS on 2019-06-04. Version history is recorded from 2026-11-11. Earlier versions are in the IAM console under Policy versions.
Attach snippets
AWS CLI
aws iam attach-role-policy --role-name ROLE_NAME --policy-arn arn:aws:iam::aws:policy/AWSResourceAccessManagerFullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AWSResourceAccessManagerFullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AWSResourceAccessManagerFullAccessCloudFormation
Resources:
ExampleRole:
Type: AWS::IAM::Role
Properties:
AssumeRolePolicyDocument: {} # replace with your trust policy
ManagedPolicyArns:
- arn:aws:iam::aws:policy/AWSResourceAccessManagerFullAccessTerraform
resource "aws_iam_role_policy_attachment" "awsresourceaccessmanagerfullaccess" {
role = aws_iam_role.example.name
policy_arn = "arn:aws:iam::aws:policy/AWSResourceAccessManagerFullAccess"
}CDK (TypeScript)
role.addManagedPolicy(
iam.ManagedPolicy.fromAwsManagedPolicyName("AWSResourceAccessManagerFullAccess"),
);Sources
- AWSResourceAccessManagerFullAccess (AWS Managed Policy Reference Guide) (retrieved ; supports summary, practicalScope, useCases, securityConsiderations, assignmentGuidance, faqs)
- AWS managed policies for AWS Resource Access Manager (AWS RAM User Guide) (retrieved ; supports summary, practicalScope, useCases, securityConsiderations, assignmentGuidance, faqs)
- AWS managed policies for job functions (IAM User Guide) (retrieved ; supports bestPractices, faqs)
- Managed policies and inline policies (IAM User Guide) (retrieved ; supports securityConsiderations, faqs)