Quotas for AWS Organizations
This section specifies quotas that affect AWS Organizations.
Naming guidelines
The following are guidelines for names that you create in AWS Organizations, including names of accounts, organizational units (OUs), roots, and policies:
-
They must be composed of Unicode characters
-
Maximum string length for names vary by the object. To see actual limit for each, see the AWS Organizations API Reference and find the API operation that creates the object. Look at the details for that operation's
Name
parameter. For example: Account name, or OU name.
Maximum and minimum values
The following are the default maximums for entities in AWS Organizations.
Note
You can request increases for some of these values by using the Service Quotas console
Organizations is a global service that is physically hosted in the US East (N. Virginia)
Region (us-east-1
). Therefore, you must use us-east-1
to
access Organizations quotas when using the Service Quotas console, the AWS CLI, or an AWS
SDK.
Number of AWS accounts in an organization |
10 — The default maximum number of accounts allowed in an
organization. If you need more, you can request an increase by using the
Service Quotas console An invitation sent to an account counts against this quota. The count is returned if the invited account declines, the management account cancels the invitation, or the invitation expires. Newly created accounts and organizations may experience a quota below the default of 10 accounts. |
Number of roots in an organization |
1 |
Number of OUs in an organization |
1000 |
Number of policies of each type in an organization |
1000 per policy type |
Maximum size of a policy document |
Service control policies: 5120 characters AI services opt-out policies: 2500 characters Backup policies: 10,000 characters Tag policies: 10,000 characters Note: If you save the policy by using the AWS Management Console, extra white space (such as spaces and line breaks) between JSON elements and outside of quotation marks, is removed and not counted. If you save the policy using an SDK operation or the AWS CLI, then the policy is saved exactly as you provided and no automatic removal of characters occurs. |
OU maximum nesting in a root |
Five levels of OUs deep under a root. |
Maximum number of invitation attempts you can perform in a 24-hour period |
Either 20 or the maximum number of accounts allowed in your organization, whichever is greater. Accepted invitations don't count against this quota. As soon as one invitation is accepted, you can send another invitation that same day. If the maximum number of accounts allowed in your organization is less than 20, then you get an "account limit exceeded" exception if you attempt to invite more accounts than your organization can contain. However, you can cancel invitations and send new ones up to the maximum of 20 attempts in one day. |
Number of member accounts you can create concurrently |
5 — As soon as one finishes, you can start another, but only five can be in progress at a time. |
Number of member accounts you can close in a 30-day period | 10% of member accounts in an organization, with a maximum of 200.
For example, if you have 2,500 member accounts, you can close up
to 200 (not 250) accounts in a 30-day period. After you reach this
quota, you can close additional accounts in the AWS Billing console |
Number of member accounts you can close concurrently | 3 — Only three account closures can be in progress at the same time. As soon as one finishes, you can close another account. |
Number of entities to which you can attach a policy |
Unlimited |
Number of tags that you can attach to a root, OU, or account |
50 |
Maximum size of the resource-based delegation policy | 40,000 characters |
Expiration times for handshakes
The following are the timeouts for handshakes in AWS Organizations.
Invitation to join an organization |
15 days |
Request to enable all features in an organization |
90 days |
Handshake is deleted and no longer appears in lists |
30 days after the handshake is completed |
Number of policies that you can attach to an entity
The minimum and maximum depend on the policy type and the entity that you're attaching the policy to. The following table shows each policy type and the number of entities that you can attach each type to.
Note
These numbers apply to only those policies that are directly attached to an OU or an account. Policies that affect an OU or account by inheritance do not count against these limits.
Policy type | Minimum attached to an entity | Maximum attached to root | Maximum attached per OU | Maximum attached per account |
---|---|---|---|---|
Service control policy | 1 — Every entity must have at least one SCP attached at all times. You can't remove the last SCP from an entity. | 5 | 5 | 5 |
AI services opt-out policy | 0 | 5 | 5 | 5 |
Backup policy | 0 | 10 | 10 | 10 |
Tag policy | 0 | 10 | 10 | 10 |
Note
Currently, you can have only one root in an organization.