AWS Organizations
User Guide

Creating an AWS Account in Your Organization

An organization is a collection of AWS accounts that you centrally manage. You can perform the following procedures to manage the accounts that are part of your organization:


When you create an account this way, you automatically grant full administrative control for the member account through an IAM role. This role, created in the member account, enables IAM users in the master account to exercise full administrative control over the member account. Note that this role is subject to any service control policies (SCPs) that apply to the account.

Creating an AWS Account That Is Part of Your Organization

When signed in to the organization's master account, you can create member accounts that are automatically part of your organization. To do this, complete the following steps.

Minimum permissions

To create a member account in your organization, you must have the following permission:

  • organizations:DescribeOrganization (console only)

  • organizations:CreateAccount


When you create an account using the following procedure, AWS does not automatically collect all the information required for an account to operate as a standalone account. If you ever need to remove the account from the organization and make it a standalone account, then you must first provide that information for the account. Only then can you remove it from the organization. For more information, see To leave an organization when all required account information has not yet been provided (console).

To create an AWS account that automatically is part of your organization (Console)

  1. Sign in to the Organizations console at You must sign in as an IAM user, assume an IAM role, or sign in as the root user (not recommended) in the organization's master account.

  2. On the Accounts tab, choose Add account.

  3. Choose Create account.

  4. Type the name that you want to assign to the account. This is essentially a description to help you distinguish the account later from all other accounts in the organization, and is separate from the IAM alias or the email name of the owner.

  5. Type the email address for the owner of the new account. This must be unique to this account, because it can be used to sign in as the root user of the account.

  6. (Optional) Specify the name to be assigned to the IAM role that is automatically created in the new account. This role grants the organization's master account permission to access the newly created member account. If you do not specify a name, AWS Organizations gives the role a default name of OrganizationAccountAccessRole.


    Remember this role name. You need it later to grant access to the new account for IAM users in the master account.

  7. Choose Create.


    If you get an exception that indicates that you exceeded your account limits for the organization or that you can't add an account because your organization is still initializing, please contact AWS Customer Support.

  8. You are redirected to the Accounts/All accounts tab, showing your new account at the top of the list with its status set to Pending creation. This status changes to Active when the account is created.


    By default, the Accounts tab hides account creation requests that failed. To show these, choose the switch at the top of the list and change it to Show.

  9. Now that the account exists and has an IAM role that grants admin access to users in the master account, you can access the account by following the steps in Accessing and Administering the Member Accounts in Your Organization.

To create an AWS account that is automatically part of your organization (AWS CLI, AWS API)

You can use the following commands to create an account: