📄️ Deploy the Stax-Provisioning Role to Allow Stax Onboarding
Before you can perform some Stax onboarding operations, the Stax-Provisioning IAM role must be deployed into AWS accounts. You should deploy this role only when required as part of Stax's onboarding operations or when requested by Customer Support.
📄️ Migrate a Stax-managed AWS account to another AWS Organization
Moving an AWS account between AWS Organizations is a well-defined process. AWS provides guidance on this. When the account is being moved from a Stax-managed AWS Organization to another AWS Organization, there are additional considerations.
📄️ Offboarding your AWS Organization from Stax
Should your organization decide to remove Stax from its AWS environment, there are a series of steps that must be completed in order to successfully do this. These steps should be completed in consultation with the Customer Support team or your Customer Success Manager. Before you begin the offboarding process, be aware that:
📄️ Onboard an AWS Account to Stax
Stax allows you to onboard existing AWS accounts that have been discovered from an AWS Organization created outside of Stax. Onboarding accounts to Stax gives you the ability to manage all of your AWS Accounts centrally within Stax and fully leverage its benefits and features.
📄️ Onboard an AWS Organization to Stax
Before Stax can complete the onboarding operations for your AWS Organization, you must first perform some preparation tasks.
📄️ Reconfigure Services to Prepare for Stax Onboarding
When onboarding an account or organization to Stax, several services require configuration for the Stax Assurance processes to be successful.
📄️ Stax Onboarding FAQ
## Why does Stax need access to AWS Accounts?