Creates an AWS account that is automatically a member of the
organization whose credentials made the request. This is an asynchronous
request that AWS 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:
organizations_create_account(Email, AccountName, RoleName,
IamUserAccessToBilling)[required] The email address of the owner to assign to the new member account. This email address must not already be associated with another AWS account. You must use a valid email address to complete account creation. You can't access the root user of the account or remove an account that was created with an invalid email address.
[required] The friendly name of the member account.
(Optional)
The name of an IAM role that AWS Organizations automatically preconfigures in the new member account. This role trusts the master account, allowing users in the master account to assume the role, as permitted by the master account administrator. The role has administrator permissions in the new member account.
If you don't specify this parameter, the role name defaults to
OrganizationAccountAccessRole.
For more information about how to use this role to access the member account, see Accessing and Administering the Member Accounts in Your Organization in the AWS Organizations User Guide, and steps 2 and 3 in Tutorial: Delegate Access Across AWS Accounts Using IAM Roles in the IAM User Guide.
The regex pattern that is used to validate this parameter is a string of characters that can consist of uppercase letters, lowercase letters, digits with no spaces, and any of the following characters: =,.@-
If set to ALLOW, the new account enables IAM users to access account
billing information if they have the required permissions. If set to
DENY, only the root user of the new account can access account billing
information. For more information, see Activating Access to the Billing and Cost Management Console
in the AWS Billing and Cost Management User Guide.
If you don't specify this parameter, the value defaults to ALLOW, and
IAM users and roles with the required permissions can access billing
information for the new account.
svc$create_account( Email = "string", AccountName = "string", RoleName = "string", IamUserAccessToBilling = "ALLOW"|"DENY" )
Use the OperationId response element from this operation to
provide as a parameter to the DescribeCreateAccountStatus operation.
Check the AWS CloudTrail log for the CreateAccountResult event.
For information on using AWS CloudTrail with Organizations, see
Monitoring the Activity in Your Organization
in the AWS 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, AWS Organizations will create the required
service-linked role named AWSServiceRoleForOrganizations. For more
information, see AWS Organizations and Service-Linked Roles
in the AWS Organizations User Guide.
AWS Organizations preconfigures the new member account with a role
(named OrganizationAccountAccessRole by default) that grants users in
the master account administrator permissions in the new member account.
Principals in the master account can assume the role. AWS Organizations
clones the company name and address information for the new account from
the organization's master account.
This operation can be called only from the organization's master account.
For more information about creating accounts, see Creating an AWS Account in Your Organization in the AWS Organizations User Guide.
When you create an account in an organization using the AWS 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 AWS Organizations User Guide.
If you get an exception that indicates that you exceeded your account limits for the organization, contact AWS 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 AWS 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 AWS Account in the AWS 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.
# NOT RUN {
# The owner of an organization creates a member account in the
# organization. The following example shows that when the organization
# owner creates the member account, the account is preconfigured with the
# name "Production Account" and an owner email address of
# susan@example.com. An IAM role is automatically created using the
# default name because the roleName parameter is not used. AWS
# Organizations sends Susan a "Welcome to AWS" email:
#
#
# }
# NOT RUN {
svc$create_account(
AccountName = "Production Account",
Email = "susan@example.com"
)
# }
# NOT RUN {
# }
Run the code above in your browser using DataCamp Workspace