Skip to main content
IAM Policy Map

ResourceGroupsandTagEditorFullAccess

AdminAWS managedActiveReviewedShow on mapCompare

Summary

Provides full access to Resource Groups and Tag Editor. The Resource Groups User Guide says it grants the permissions required for full access to Resource Groups and Tag Editor functionality.

Permissions imported from the AWS Managed Policy Reference Guide; other sections reviewed against the listed AWS sources.

Identity

ARN
arn:aws:iam::aws:policy/ResourceGroupsandTagEditorFullAccess
Default version
v6
Created
Last edited
Services
cloudformation, resource-groups, tag

Control-plane actions (37)

By access level: 9 List, 10 Read, 4 Tagging, 14 Write.

Control-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
CloudFormation3 of 1043 List; 0 restricted, 0 conditionalcloudformation:DescribeStacks, cloudformation:ListStackResources, cloudformation:ListStacks
Resource GroupsAll 29 actions (see the Resource Groups page)6 List, 7 Read, 2 Tagging, 14 Write; 0 restricted, 0 conditionalresource-groups:*
Resource Group Tagging5 of 93 Read, 2 Tagging; 0 restricted, 0 conditionaltag:TagResources, tag:UntagResources, tag:getResources, tag:getTagKeys, tag:getTagValues
CloudFormation: 3 actions
  • cloudformation:DescribeStacks (List)
  • cloudformation:ListStackResources (List)
  • cloudformation:ListStacks (List)
Resource Group Tagging: 5 actions
  • tag:GetResources (Read)
  • tag:GetTagKeys (Read)
  • tag:GetTagValues (Read)
  • tag:TagResources (Tagging)
  • tag:UntagResources (Tagging)

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: resource-groups (14 of 14).

Guidance

Practical scope

One statement with 9 entries, all on Resource "*": tag:getResources, tag:getTagKeys, tag:getTagValues, tag:TagResources, tag:UntagResources, resource-groups:*, cloudformation:DescribeStacks, cloudformation:ListStackResources and cloudformation:ListStacks.

Use cases

  • Give users or roles full access to Resource Groups and Tag Editor, including tag:TagResources and tag:UntagResources.

Best practices

  • The AWS Resource Groups User Guide says AWS managed policies might not grant least-privilege permissions for your specific use cases and recommends reducing permissions further with customer managed policies specific to your use cases.

Security considerations

  • tag:TagResources and tag:UntagResources on Resource "*" let principals add and remove tags on resources, and resource-groups:* allows every Resource Groups action.
  • It also reads CloudFormation stack and stack resource information (cloudformation:DescribeStacks, cloudformation:ListStackResources, cloudformation:ListStacks).
  • 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 access to Resource Groups and Tag Editor is intended.

Related policies

Same service

Same domain

Frequently asked questions

When should I attach ResourceGroupsandTagEditorFullAccess?
The reference page says you can attach ResourceGroupsandTagEditorFullAccess to your users, groups and roles, and describes it as: provides full access to Resource Groups and Tag Editor. Attach it where managing resource groups and tags is the intended scope.
What does ResourceGroupsandTagEditorFullAccess grant?
It allows tag:getResources, tag:getTagKeys, tag:getTagValues, tag:TagResources and tag:UntagResources, resource-groups:*, and three read actions on CloudFormation stacks, all on all resources.
What are the security risks of ResourceGroupsandTagEditorFullAccess?
tag:TagResources, tag:UntagResources and resource-groups:* are write-capable on all resources. AWS managed policies don't grant least privilege permissions, and you must consider the security risk of granting principals more permissions than they need. AWS updates to the policy affect every identity it is attached to.

Policy JSON

Download policy.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "tag:getResources",
        "tag:getTagKeys",
        "tag:getTagValues",
        "tag:TagResources",
        "tag:UntagResources",
        "resource-groups:*",
        "cloudformation:DescribeStacks",
        "cloudformation:ListStackResources",
        "cloudformation:ListStacks"
      ],
      "Resource": "*"
    }
  ]
}

Version history

Current version v6, edited by AWS on 2023-08-10. 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/ResourceGroupsandTagEditorFullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/ResourceGroupsandTagEditorFullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/ResourceGroupsandTagEditorFullAccess

CloudFormation

Resources:
  ExampleRole:
    Type: AWS::IAM::Role
    Properties:
      AssumeRolePolicyDocument: {}  # replace with your trust policy
      ManagedPolicyArns:
        - arn:aws:iam::aws:policy/ResourceGroupsandTagEditorFullAccess

Terraform

resource "aws_iam_role_policy_attachment" "resourcegroupsandtageditorfullaccess" {
  role       = aws_iam_role.example.name
  policy_arn = "arn:aws:iam::aws:policy/ResourceGroupsandTagEditorFullAccess"
}

CDK (TypeScript)

role.addManagedPolicy(
  iam.ManagedPolicy.fromAwsManagedPolicyName("ResourceGroupsandTagEditorFullAccess"),
);

Sources