Accessing and administering the member accounts in your organization - AWS Organizations

Accessing and administering the member accounts in your organization

When you create an account in your organization, in addition to the root user, AWS Organizations automatically creates an IAM role that is by default named OrganizationAccountAccessRole. You can specify the name when you create it. We refer to the role in this guide by that default name. However, AWS Organizations doesn't create any other IAM users, groups, or other roles. To access the accounts in your organization, you must use one of the following methods:

Minimum permissions

To access an AWS account from any other account in your organization, you must have the following permission:

  • sts:AssumeRole – The Resource element must be set to either an asterisk (*) or the account ID number of the account with the user who needs to access the new member account

Accessing a member account as the root user

When you create a new account, AWS Organizations initially assigns a password to the root user that is a minimum of 64 characters long. All characters are randomly generated with no guarantees on the appearance of certain character sets. You can't retrieve this initial password. To access the account as the root user for the first time, you must go through the process for password recovery.

Notes
  • As a best practice, we recommend that you don't use the root user to access your account except to create other users and roles with more limited permissions. Then sign in as one of those users or roles.

  • We also recommend that you set multi-factor authentication (MFA) on the root user. Reset the password, and assign an MFA device to the root user.

  • If you created a member account in an organization with an incorrect email address, you can’t sign in to the account as the root user. Contact AWS Billing and Support for assistance.

To request a new password for the root user of the member account (console)

  1. Go to the Sign in page of the AWS console at https://console.aws.amazon.com/. If you are already signed in to AWS, you have to sign out to see the sign-in page.

  2. If the Sign in page shows three text boxes for Account ID or alias, IAM user name, and Password, choose Sign in using root account credentials.

  3. Enter the email address that is associated with your AWS account and then choose Next.

  4. Choose Forgot your password? and then enter the information that is required to reset the password to a new one that you provide. To do this, you must be able to access incoming mail sent to the email address that is associated with the account.

Creating the OrganizationAccountAccessRole in an invited member account

By default, if you create a member account as part of your organization, AWS automatically creates a role in the account that grants administrator permissions to delegated IAM users in the master account. By default, that role is named OrganizationAccountAccessRole. For more information, see Accessing a member account that has a master account access role.

However, member accounts that you invite to join your organization do not automatically get an administrator role created. You have to do this manually, as shown in the following procedure. This essentially duplicates the role automatically set up for created accounts. We recommend that you use the same name, OrganizationAccountAccessRole, for your manually created roles for consistency and ease of remembering.

To create an AWS Organizations administrator role in a member account (console)

  1. Sign in to the IAM console at https://console.aws.amazon.com/iam/. You must sign in as an IAM user, assume an IAM role, or sign in as the root user (not recommended) in the member account that has permissions to create IAM roles and policies.

  2. In the IAM console, navigate to Roles and then choose Create Role.

  3. Choose Another AWS account.

  4. Enter the 12-digit account ID number of the master account that you want to grant administrator access to and choose Next: Permissions.

    For this role, because the accounts are internal to your company, you should not choose Require external ID. For more information about the external ID option, see When Should I Use the External ID? in the IAM User Guide.

  5. If you have MFA enabled and configured, you can optionally choose to require authentication using an MFA device. For more information about MFA, see Using Multi-Factor Authentication (MFA) in AWS in the IAM User Guide.

  6. On the Attach permissions policies page, choose the AWS managed policy named AdministratorAccess and then choose Next: Tags.

  7. On the Add tags (optional) page, choose Next: Review.

  8. On the Review page, specify a role name and an optional description. We recommend that you use OrganizationAccountAccessRole, for consistency with the default name assigned to the role in new accounts. To commit your changes, choose Create role.

  9. Your new role appears on the list of available roles. Choose the new role's name to view the details, paying special note to the link URL that is provided. Give this URL to users in the member account who need to access the role. Also, note the Role ARN because you need it in step 15.

  10. Sign in to the IAM console at https://console.aws.amazon.com/iam/. This time, sign in as a user in the master account who has permissions to create policies and assign the policies to users or groups.

  11. Navigate to Policies and then choose Create Policy.

    Note

    This example shows how to create a policy and attach it to a group. If you already created this policy for other accounts, skip to step 18

  12. For Service, choose STS.

  13. For Actions, start typing AssumeRole in the Filter box and then select the check box next to it when it appears.

  14. Choose Resources, ensure that Specific is selected and then choose Add ARN.

  15. Enter the AWS member account ID number and then enter the name of the role that you previously created in steps 1–8. Choose Add.

  16. If you're granting permission to assume the role in multiple member accounts, repeats steps 14 and 15 for each account.

  17. Choose Review policy.

  18. Enter a name for the new policy and then choose Create policy to save your changes.

  19. Choose Groups in the navigation pane and then choose the name of the group (not the check box) that you want to use to delegate administration of the member account.

  20. Choose the Permissions tab.

  21. Choose Attach Policy, select the policy that you created in steps 11–18, and then choose Attach Policy.

The users who are members of the selected group now can use the URLs that you captured in step 9 to access each member account's role. They can access these member accounts the same way as they would if accessing an account that you create in the organization. For more information about using the role to administer a member account, see Accessing a member account that has a master account access role.

Accessing a member account that has a master account access role

When you create a member account using the AWS Organizations console, AWS Organizations automatically creates an IAM role named OrganizationAccountAccessRole in the account. This role has full administrative permissions in the member account. The role is also configured to grant that access to the organization's master account. You can create an identical role for an invited member account by following the steps in Creating the OrganizationAccountAccessRole in an invited member account. To use this role to access the member account, you must sign in as a user from the master account that has permissions to assume the role. To configure these permissions, perform the following procedure. We recommend that you grant permissions to groups instead of users for ease of maintenance.

To grant permissions to members of an IAM group in the master account to access the role (console)

  1. Sign in to the IAM console at https://console.aws.amazon.com/iam/ as a user with administrator permissions in the master account. This is required to delegate permissions to the IAM group whose users will access the role in the member account.

  2. Start by creating the managed policy that you need later in Step 11.

    In the navigation pane, choose Policies and then choose Create policy.

  3. On the Visual editor tab, choose Choose a service, type STS in the search box to filter the list, and then choose the STS option.

  4. In the Actions section, type assume in the search box to filter the list, and then choose the AssumeRole option.

  5. In the Resources section, choose Specific, choose Add ARN to restrict access, and then type the member account number and the name of the role that you created in the previous section (we recommended naming it OrganizationAccountAccessRole).

  6. Choose Add when the dialog box displays the correct ARN.

  7. (Optional) If you want to require multi-factor authentication (MFA), or restrict access to the role from a specified IP address range, then expand the Request conditions section, and select the options you want to enforce.

  8. Choose Review policy.

  9. In the Name field, enter a name for your policy. For example : GrantAccessToOrganizationAccountAccessRole. You can also add an optional description.

  10. Choose Create policy to save your new managed policy.

  11. Now that you have the policy available, you can attach it to a group.

    In the navigation pane, choose Groups and then choose the name of the group (not the check box) whose members you want to be able to assume the role in the member account. If necessary, you can create a new group.

  12. Choose the Permissions tab and then under Managed Policies, choose Attach policy.

  13. (Optional) In the Search box, you can start typing the name of your policy to filter the list until you can see the name of the policy you just created in Step 2 through Step 10. You can also filter out all of the AWS managed policies by choosing Policy Type and then choosing Customer Managed.

  14. Check the box next to your policy, and then choose Attach Policy.

IAM users that are members of the group now have permissions to switch to the new role in the AWS Organizations console by following the below procedure.

To switch to the role for the member account (console)

When using the role, the user has administrator permissions in the new member account. Instruct your IAM users who are members of the group to do the following to switch to the new role.

  1. From the upper-right corner of the AWS Organizations console, choose the link that contains the current sign-in name and then choose Switch Role.

  2. Enter the administrator-provided account ID number and role name.

  3. For Display Name, enter the text that you want to show on the navigation bar in the upper-right corner in place of your user name while you are using the role. You can optionally choose a color.

  4. Choose Switch Role. Now all actions that you perform are done with the permissions granted to the role that you switched to. You no longer have the permissions associated with your original IAM user until you switch back.

  5. When you finish performing actions that require the permissions of the role, you can switch back to your normal IAM user. Choose the role name in the upper-right corner (whatever you specified as the Display Name) and then choose Back to UserName.

Additional resources