[Troubleshooting]

Owned by Daria Lebedeva
Last updated: Sept 18, 2024
1 min read

 

Troubleshooting

 

If you do not see any AWS Organizations, there are two possible reasons:

  1. Insufficient permissions on AWS Organizations Master Account.

  2. AWS Organizations Master Account has not been added to Cloudaware.

If the 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.

 

Identify AWS Organizational Accounts that got onboarded successfully

 

  1. In Cloudaware CMDB Navigator, go to AMAZON WEB SERVICES → Security, Identity, Compliance → Organizations.

  1. You should see at least one AWS Organization and N number of AWS Organizational Accounts.

 

Identify AWS Organizational Accounts that didn't get onboarded successfully

 

  1. In Cloudaware CMDB Navigator, go to AMAZON WEB SERVICES → Security, Identity, Compliance → AWS Organizational Accounts.

  1. Click Browse Objects:

  1. Paste the following query and click Search:

`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 accounts where 'Actual Account' is blank can't be automatically added since Cloudaware is unable to assume its IAM role.

Â