ROLE-BASED ACCESS NOTE: Some of the features and functionality described in this article require the assignment of the Admin or the DevOps user role to your user account. Without one of these roles assigned, some or all of the functionality may not be available to you.
Aimably is configured to work with multiple AWS accounts configured in a single AWS organization or across multiple AWS organizations.
Connecting to All Accounts in an AWS Organization
To ensure Aimably has access to all AWS member accounts, ensure you are signed into the managing account when performing the AWS connection steps. Aimably will establish its connection through the managing account, then access all member accounts from that role automatically. You can confirm Aimably access to all accounts in an AWS organization by reviewing the architecture diagram that appears once the sync is complete.
Connecting to Multiple Unrelated AWS Accounts or Organizations
To ensure Aimably has access to all of your independent AWS accounts or organizations, you will need to perform AWS connection steps for each of the unrelated managing accounts. Follow the basic AWS connection steps using the Cloud Accounts Wizard for the first managing account, then revisit these steps again for each subsequent account.
Note: In the case of multiple independent AWS accounts, each can have its own AWS policy permissions configured.
For more information on Aimably's connection with AWS, please refer to this guide: FAQ: Understanding How Aimably Retrieves AWS Account Data