You can create an organization with your AWS account as the management account. When you create an organization, you can choose whether the organization supports all features (recommended) or only consolidated billing. By default, an organization you create supports all features.
Create an organizationYou can create an organization by using either the AWS Management Console or by using a command from the AWS CLI or one of the SDK APIs.
Minimum permissionsTo create an organization with your current AWS account, you must have the following permissions:
organizations:CreateOrganization
iam:CreateServiceLinkedRole
You can restrict this permission to only the service principal organizations.amazonaws.com.
Sign in to the AWS Organizations console. 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 management account.
By default, the organization is created with all features enabled. However, you can choose either of the following steps:
To create an organization with all features enabled, on the introduction page, choose Create an organization.
To create an organization with Consolidated Billing features only, on the introduction page and under Create an organization, choose consolidated billing features, and then in the confirmation dialog box, choose Create an organization.
If you accidentally choose the wrong option, you can immediately go to the Settings page, and then choose Delete organization and start over.
The organization is created and the AWS accounts page appears. The only account present is your management account, and it's currently stored in the root organizational unit (OU).
If required, Organizations automatically sends a verification email to the address that is associated with your management account. There might be a delay before you receive the verification email. Verify your email address within 24 hours. For more information, see Email address verification with AWS Organizations. You can create accounts to grow your organization without verifying your management account's email address. However, to invite existing accounts, you must first complete email verification.
NoteIf this account previously verified its email address, then it doesn't happen again when you use the account to create an organization.
The following code examples show how to use CreateOrganization.
using System;
using System.Threading.Tasks;
using Amazon.Organizations;
using Amazon.Organizations.Model;
/// <summary>
/// Creates an organization in AWS Organizations.
/// </summary>
public class CreateOrganization
{
/// <summary>
/// Creates an Organizations client object and then uses it to create
/// a new organization with the default user as the administrator, and
/// then displays information about the new organization.
/// </summary>
public static async Task Main()
{
IAmazonOrganizations client = new AmazonOrganizationsClient();
var response = await client.CreateOrganizationAsync(new CreateOrganizationRequest
{
FeatureSet = "ALL",
});
Organization newOrg = response.Organization;
Console.WriteLine($"Organization: {newOrg.Id} Main Accoount: {newOrg.MasterAccountId}");
}
}
Example 1: To create a new organization
Bill wants to create an organization using credentials from account 111111111111. The following example shows that the account becomes the master account in the new organization. Because he does not specify a features set, the new organization defaults to all features enabled and service control policies are enabled on the root.
aws organizations create-organization
The output includes an organization object with details about the new organization:
{
"Organization": {
"AvailablePolicyTypes": [
{
"Status": "ENABLED",
"Type": "SERVICE_CONTROL_POLICY"
}
],
"MasterAccountId": "111111111111",
"MasterAccountArn": "arn:aws:organizations::111111111111:account/o-exampleorgid/111111111111",
"MasterAccountEmail": "bill@example.com",
"FeatureSet": "ALL",
"Id": "o-exampleorgid",
"Arn": "arn:aws:organizations::111111111111:organization/o-exampleorgid"
}
}Example 2: To create a new organization with only consolidated billing features enabled
The following example creates an organization that supports only the consolidated billing features:
aws organizations create-organization --feature-set CONSOLIDATED_BILLING
The output includes an organization object with details about the new organization:
{
"Organization": {
"Arn": "arn:aws:organizations::111111111111:organization/o-exampleorgid",
"AvailablePolicyTypes": [],
"Id": "o-exampleorgid",
"MasterAccountArn": "arn:aws:organizations::111111111111:account/o-exampleorgid/111111111111",
"MasterAccountEmail": "bill@example.com",
"MasterAccountId": "111111111111",
"FeatureSet": "CONSOLIDATED_BILLING"
}
}For more information, see Creating an Organization in the AWS Organizations Users Guide.
After you have created an organization, you can add accounts to your organization in these ways from the management account:
Managing an entire organization
Verifying your email address
Did this page help you? - Yes
Thanks for letting us know we're doing a good job!
If you've got a moment, please tell us what we did right so we can do more of it.
Did this page help you? - No
Thanks for letting us know this page needs work. We're sorry we let you down.
If you've got a moment, please tell us how we can make the documentation better.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4