| Info |
|---|
AWS Organizations is a Policy-based management for multiple AWS accounts. |
...
Using AWS Organizations, you can create Service Control Policies (SCPs) that centrally control AWS service use across multiple AWS accounts. You can also use Organizations to help automate the creation of new accounts through APIs. Organizations helps simplify the billing for multiple accounts by enabling you to setup a single payment method for all the accounts in your organization through consolidated billing. AWS Organizations is available to all AWS customers at no additional charge. More information can be found here.
...
Benefits Of Using AWS Organizations In Cloudaware
No need to manually add every AWS account
Automate on-boarding of your AWS Accounts into Cloudaware
Ability to see which AWS Organizational Accounts exist but are not in Cloudaware CMDB as AWS Accounts.
Adding AWS Organization
...
To Cloudaware
1. Log in to Cloudaware account → Admin → Amazon Organizations & Accounts. Click +Add.
2. Address Cloudaware AWS Start Guide to add AWS Organizations Master Account using IAM Role integration type.
...
| Code Block |
|---|
"organizations:Des*" "organizations:Li*" |
4. Click Check → Save. Go back to Admin → Organizations & Amazon Accounts → N configured → the tab ‘Accounts' to ensure AWS Organizations Organization Master Account has a green status indicator.
5. Select the tab 'Organizations' → click +Add Amazon Organization. Fill out the form selecting your Organization Master Account in Trusted Account. Click Check → Save.
6. In Cloudaware navigate to AMAZON WEB SERVICES → Security, Identity, Compliance → Organizations. AWS Organization should be visible in Cloudaware.
...
If you do not see any AWS Organizations, there are two possible reasons:
Insufficient permissions on AWS Organizations Master Account.
AWS Organizations Master Account has not been added to Cloudaware.
If AWS Organization Master Account has been added to Cloudaware but auto-collection doesn't take place, check if Role Name and External ID are custom as they shouldn't be left auto-populated by Cloudaware during the StackSet creation.
...