Post x amz targetawsorganizationsv20161128.createaccount

v1

latestOpenAPI 3.0.0Apache 2.0 License2026-07-1455233317.4 KB

Creates an Amazon Web Services account that is automatically a member of the organization whose credentials made the request. This is an asynchronous request that Amazon Web Services performs in the background. Because CreateAccount operates asynchronously, it can return a successful completion message even though account initialization might still be in progress. You might need to wait a few minutes before you can successfully access the account. To check the status of the request, do one of the following:

Use the Id value of the CreateAccountStatus response element from this operation to provide as a parameter to the DescribeCreateAccountStatus operation.
Check the CloudTrail log for the CreateAccountResult event. For information on using CloudTrail with Organizations, see Logging and monitoring in Organizations in the Organizations User Guide.

The user who calls the API to create an account must have the organizations:CreateAccount permission. If you enabled all features in the organization, Organizations creates the required service-linked role named AWSServiceRoleForOrganizations. For more information, see Organizations and Service-Linked Roles in the Organizations User Guide.

If the request includes tags, then the requester must have the organizations:TagResource permission.

Organizations preconfigures the new member account with a role (named OrganizationAccountAccessRole by default) that grants users in the management account administrator permissions in the new member account. Principals in the management account can assume the role. Organizations clones the company name and address information for the new account from the organization's management account.

This operation can be called only from the organization's management account.

For more information about creating accounts, see Creating an Amazon Web Services account in Your Organization in the Organizations User Guide.

When you create an account in an organization using the Organizations console, API, or CLI commands, the information required for the account to operate as a standalone account, such as a payment method and signing the end user license agreement (EULA) is not automatically collected. If you must remove an account from your organization later, you can do so only after you provide the missing information. Follow the steps at To leave an organization as a member account in the Organizations User Guide.
If you get an exception that indicates that you exceeded your account limits for the organization, contact Amazon Web Services Support.
If you get an exception that indicates that the operation failed because your organization is still initializing, wait one hour and then try again. If the error persists, contact Amazon Web Services Support.
Using CreateAccount to create multiple temporary accounts isn't recommended. You can only close an account from the Billing and Cost Management console, and you must be signed in as the root user. For information on the requirements and process for closing an account, see Closing an Amazon Web Services account in the Organizations User Guide.

When you create a member account with this operation, you can choose whether to create the account with the IAM User and Role Access to Billing Information switch enabled. If you enable it, IAM users and roles that have appropriate permissions can view billing information for the account. If you disable it, only the account root user can access billing information. For information about how to disable this switch for an account, see Granting Access to Your Billing Information and Tools.

post/#X-Amz-Target=AWSOrganizationsV20161128.CreateAccount

Headers

X-Amz-Target'AWSOrganizationsV20161128.CreateAccount' required

Request body

Emailstring password required

The email address of the owner to assign to the new member account. This email address must not already be associated with another Amazon Web Services account. You must use a valid email address to complete account creation. The rules for a valid email address: <ul> <li> The address must be a minimum of 6 and a maximum of 64 characters long. </li> <li> All characters must be 7-bit ASCII characters. </li> <li> There must be one and only one @ symbol, which separates the local name from the domain name. </li> <li> The local name can't contain any of the following characters: whitespace, " ' ( ) < > [ ] : ; , \ | % & </li> <li> The local name can't begin with a dot (.) </li> <li> The domain name can consist of only the characters [a-z],[A-Z],[0-9], hyphen (-), or dot (.) </li> <li> The domain name can't begin or end with a hyphen (-) or dot (.) </li> <li> The domain name must contain at least one dot </li> </ul> You can't access the root user of the account or remove an account that was created with an invalid email address.

AccountNamestring password required

The friendly name of the member account.

RoleNamestring

The name of an IAM role that Organizations automatically preconfigures in the new member account. This role trusts the management account, allowing users in the management account to assume the role, as permitted by the management account administrator. The role has administrator permissions in the new member account. If you don't specify this parameter, the role name defaults to <code>OrganizationAccountAccessRole</code>. For more information about how to use this role to access the member account, see the following links: <ul> <li> <a href="https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts_access.html#orgs_manage_accounts_create-cross-account-role">Accessing and Administering the Member Accounts in Your Organization</a> in the Organizations User Guide </li> <li> Steps 2 and 3 in <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_cross-account-with-roles.html">Tutorial: Delegate Access Across Amazon Web Services accounts Using IAM Roles</a> in the IAM User Guide </li> </ul> The <a href="http://wikipedia.org/wiki/regex">regex pattern</a> that is used to validate this parameter. The pattern can include uppercase letters, lowercase letters, digits with no spaces, and any of the following characters: =,.@-

IamUserAccessToBilling'ALLOW' | 'DENY'

If set to <code>ALLOW</code>, the new account enables IAM users to access account billing information if they have the required permissions. If set to <code>DENY</code>, only the root user of the new account can access account billing information. For more information, see <a href="https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/grantaccess.html#ControllingAccessWebsite-Activate">Activating Access to the Billing and Cost Management Console</a> in the Amazon Web Services Billing and Cost Management User Guide. If you don't specify this parameter, the value defaults to <code>ALLOW</code>, and IAM users and roles with the required permissions can access billing information for the new account.

Response

Success

Example response

{
  "CreateAccountStatus": {
    "Id": "car-examplecreateaccountrequestid111",
    "State": "IN_PROGRESS"
  }
}