Page Comparison

Anchor_uxrgn4h0vakk_uxrgn4h0vakk Anchor_j6460e38whjd_j6460e38whjdCloudaware Support For
Image Removed
Anchor_vg9fw4640ke6_vg9fw4640ke6 About AWS Organizations
Benefits Of Using AWS Organizations In Cloudaware
Requirements
Overview Checklist
STEP 1 - Cloudaware Access To AWS Organizations Master Account
STEP 2 - Cloudaware Access To AWS Organizations Sub-Accounts
STEP 3 - Notify Cloudaware Support
STEP 4 - Identify AWS Organization Accounts That Didn't Get Onboarded Successfully
Anchor_vkhxsyopuv4b_vkhxsyopuv4b

...

About AWS Organizations

AWS Organizations is a Policy-based management for multiple AWS accounts.
AWS Organizations offers policy-based management for multiple AWS accounts. With Organizations, you can create groups of accounts, automate account creation, apply and manage policies for those groups. Organizations enables you to centrally manage policies across multiple accounts, without requiring custom scripts and manual processes.

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

Anchor_qy22ir7a4vu1_qy22ir7a4vu1

...

Benefits Of Using AWS Organizations In Cloudaware

1. No need to manually add every AWS account

2. Automate on-boarding of AWS Accounts into Cloudaware

3. Ability to see which AWS Organization Accounts exist but are not in Cloudaware CMDB as AWS Accounts.

...

...

Requirements

1. Cloudaware AWS Organization Master account has been added to Cloudaware CMDB.
2. Cloudaware has following IAM permission on AWS Organization Master Account

organizations:DescribeOrganization
organizations:ListRoots
organizations:ListOrganizationalUnitsForParent
organizations:ListAccountsForParent
Anchor_kga1il755hs7_kga1il755hs7

...

...

Overview Checklist

1. Ensure AWS Organizations Master Account has a green status indicator in the Admin Panel.
2. Deploy Cloudaware CloudFormation template to all Organization Accounts
3. Request auto-adding of all AWS Organization Accounts to Cloudaware CMDB
4. AWS Organization Accounts are now visible as AWS Account objects.

...

...

...

STEP 1

...

. Cloudaware Access To AWS Organizations Master Account

1. Log in to Cloudaware CMDB and navigate to AWS Organizations.
2. You should see at least one AWS Organization and N number of AWS Organizational Accounts.

Anchor_1bfyc34eb1f7_1bfyc34eb1f7 

1. If you do not see any AWS Organizations, there are two possible reasons:
   1. Insufficient permissions on AWS Organization Master Account.
   2. AWS Organization Master Account has not been added to Cloudaware.

Double check Requirements and Overview checklist sections above.
Anchor_zd2fcfa6rhl0_zd2fcfa6rhl0

...

...

STEP 2

...

. Cloudaware Access To AWS Organizations Sub-Accounts

1. Download Cloudaware Cloudformation Template with IAM policy from the Cloudaware Admin Panel or use your custom template with policy.
2. Deploy Cloudformation template on every AWS Organizations Sub-Account.

When granting Cloudaware access to AWS Organization Sub-Account IAM External ID must be either same value or blank for all AWS Organizational Sub Accounts. See screenshot below.

If you need instructions on how to download template and execute cloudformation stack, click here.
Anchor_c1v78ey31eup_c1v78ey31eup

...

...

 STEP 3. Notify Cloudaware Support

1. Provide External ID or indicate whether it was left blank.
2. Once the request has been resolved, all AWS Organization Sub-Accounts will show up in the admin panel.

...

...

...

STEP 4

...

. Identify AWS Organization Accounts That Didn't Get Onboarded Successfully

1. Navigate to CMDB → AWS Organizations → AWS Organizational Accounts
2. Click on Browse Objects

...

Paste the following query:

`Deleted From AWS` equals null -> `AWS Organization Account Name` ASC, `Account`.`Account Name` as "Actual Account", `Account ID`, `Email`, `Joined Method`, `Joined Timestamp`, `Parent Root ARN`, `Status`

Any AWS Organizational Account where Actual Account is blank could not be auto-added successfully because Cloudaware was unable to assume IAM role in it.