Understanding the Stax Account Pool
You may notice AWS accounts in your Stax-managed AWS Organization that do not have names or resources provisioned into them. These AWS accounts, typically, are part of the Stax-managed accounts pool.
When creating a new account in AWS, it takes some time for the account to be provisioned and prepared ready for use. To reduce this time-to-service for new accounts, Stax maintains a pool of accounts for each Stax tenancy (and therefore, AWS Organization). Accounts in this pool typically have a very low monthly cost, which can be viewed on the Cost page. Stax creates these accounts in the Stax Account Pool OU in your AWS Organization.
When you create an account using Stax, an account is retrieved from the pool and configured for service. The account pool has a finite capacity, but once this action is in progress, Stax will commence creating another account to replenish the pool.
Account Pool Depletion
When a large number of accounts are created in rapid succession, there may be delays encountered if the account pool is depleted. If you anticipate needing to create a significant number of AWS accounts rapidly, please raise a support case in advance to advise the expected number of accounts. This will allow Stax to ensure that the account pool contains an appropriate number of accounts for your planned activities.
In some cases, organizations may exceed the configured AWS service limit for the number of AWS accounts in the AWS Organization. If this occurs and you are unable to create new accounts:
-
Follow the guidance in Quotas for AWS Organizations to increase your AWS Organization's AWS account limit to a higher value
-
Raise a support case with Stax's support team to have the account pool for your Stax tenancy repopulated