When should I attach AWSOrganizationsFullAccess?

Attach it to the administrators who create and fully administer your organization. The AWS Organizations User Guide says you can attach its managed policies to users or roles in your organization, and the reference page says you can attach it to users, groups and roles.

What does AWSOrganizationsFullAccess grant?

It allows organizations:* on all resources, ten account actions for contacts, account name and Regions, and iam:CreateServiceLinkedRole only for organizations.amazonaws.com.

What are the security risks of AWSOrganizationsFullAccess?

organizations:* gives full administration of the organization, and the account actions change contact details, account names and Regions. AWS managed policies don't grant least privilege permissions, and an AWS update to the policy affects every identity it is attached to.

AWSOrganizationsFullAccess

High privilegeAdminAWS managedActiveReviewedShow on map Compare

Summary

Provides full access to AWS Organizations. The AWS Organizations User Guide says it provides all of the permissions required to create and fully administer an organization.

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

Identity

ARN: arn:aws:iam::aws:policy/AWSOrganizationsFullAccess
Default version: v9
Created: 2018-11-06
Last edited: 2026-02-12
Services: account, iam, organizations

Control-plane actions (74)

By access level: 21 List, 5 Permissions management, 12 Read, 2 Tagging, 34 Write.

Control-plane actions by service
Service	Granted	Access levels and limits	Granted by
Account	10 of 20	1 List, 3 Read, 6 Write; 0 restricted, 0 conditional	account:DeleteAlternateContact, account:DisableRegion, account:EnableRegion, account:GetAccountInformation, account:GetAlternateContact, account:GetContactInformation, account:ListRegions, account:PutAccountName, account:PutAlternateContact, account:PutContactInformation
IAM	1 of 190	1 Write; 1 restricted, 1 conditional	iam:CreateServiceLinkedRole
Organizations	All 63 actions (see the Organizations page)	20 List, 5 Permissions management, 9 Read, 2 Tagging, 27 Write; 0 restricted, 0 conditional	organizations:*

Account: 10 actions

account:DeleteAlternateContact (Write)
account:DisableRegion (Write)
account:EnableRegion (Write)
account:GetAccountInformation (Read)
account:GetAlternateContact (Read)
account:GetContactInformation (Read)
account:ListRegions (List)
account:PutAccountName (Write)
account:PutAlternateContact (Write)
account:PutContactInformation (Write)

IAM: 1 actions

iam:CreateServiceLinkedRole (Write)

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: organizations (32 of 32).
Grants permissions-management actions on organizations on all resources without conditions.

Guidance

Practical scope

AWSOrganizationsFullAccess allows organizations:* on Resource "*". AWSOrganizationsFullAccessAccount allows account:PutAlternateContact, account:DeleteAlternateContact, account:GetAlternateContact, account:GetContactInformation, account:PutContactInformation, account:ListRegions, account:EnableRegion, account:DisableRegion, account:PutAccountName and account:GetAccountInformation. AWSOrganizationsFullAccessCreateSLR allows iam:CreateServiceLinkedRole when iam:AWSServiceName is organizations.amazonaws.com.

Use cases

Let an administrator create and fully administer an organization in AWS Organizations, including account contact details, account names and enabling or disabling Regions for accounts.

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

organizations:* on Resource "*" allows every AWS Organizations action, which the guide describes as everything needed to create and fully administer an organization.
The policy lets principals change account details: account:PutContactInformation, account:PutAlternateContact, account:DeleteAlternateContact, account:PutAccountName, account:EnableRegion and account:DisableRegion.
The AWS Organizations User Guide says the CreateServiceLinkedRole permission lets the policy create the service-linked role needed to create an organization, and that it is restricted to organizations.amazonaws.com.
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. The AWS Organizations User Guide says you can attach or detach its managed policies for entities in your organization. It fits the administrators of the organization.

Same service

Same domain

Frequently asked questions

When should I attach AWSOrganizationsFullAccess?: Attach it to the administrators who create and fully administer your organization. The AWS Organizations User Guide says you can attach its managed policies to users or roles in your organization, and the reference page says you can attach it to users, groups and roles.
What does AWSOrganizationsFullAccess grant?: It allows organizations:* on all resources, ten account actions for contacts, account name and Regions, and iam:CreateServiceLinkedRole only for organizations.amazonaws.com.
What are the security risks of AWSOrganizationsFullAccess?: organizations:* gives full administration of the organization, and the account actions change contact details, account names and Regions. AWS managed policies don't grant least privilege permissions, and an AWS update to the policy affects every identity it is attached to.

Policy JSON

Download policy.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "AWSOrganizationsFullAccess",
      "Effect": "Allow",
      "Action": "organizations:*",
      "Resource": "*"
    },
    {
      "Sid": "AWSOrganizationsFullAccessAccount",
      "Effect": "Allow",
      "Action": [
        "account:PutAlternateContact",
        "account:DeleteAlternateContact",
        "account:GetAlternateContact",
        "account:GetContactInformation",
        "account:PutContactInformation",
        "account:ListRegions",
        "account:EnableRegion",
        "account:DisableRegion",
        "account:PutAccountName",
        "account:GetAccountInformation"
      ],
      "Resource": "*"
    },
    {
      "Sid": "AWSOrganizationsFullAccessCreateSLR",
      "Effect": "Allow",
      "Action": "iam:CreateServiceLinkedRole",
      "Resource": "*",
      "Condition": {
        "StringEquals": {
          "iam:AWSServiceName": "organizations.amazonaws.com"
        }
      }
    }
  ]
}

Version history

Current version v9, edited by AWS on 2026-02-12. 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/AWSOrganizationsFullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AWSOrganizationsFullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AWSOrganizationsFullAccess

CloudFormation

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

Terraform

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

CDK (TypeScript)

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

Sources

AWSOrganizationsFullAccess (AWS Managed Policy Reference Guide) (retrieved 2026-11-13; supports summary, practicalScope, securityConsiderations, assignmentGuidance, faqs)
AWS managed policies for AWS Organizations (retrieved 2026-11-13; supports summary, useCases, securityConsiderations, assignmentGuidance, faqs)
Managed policies and inline policies (IAM User Guide) (retrieved 2026-11-12; supports securityConsiderations, faqs)
AWS managed policies for job functions (IAM User Guide) (retrieved 2026-11-12; supports bestPractices, faqs)