Skip to main content

Connect an AWS Account (CloudCADI hosted on AWS)

CloudCADI supports two methods for onboarding AWS Accounts:

Auto Setup and Manual Onboarding

  1. Auto Setup – Used to onboard the entire AWS Organization (Recommended approach).
  2. Manual Setup – Used to manually onboard individual AWS member accounts.

Step 1 - Navigate to Onboarding Section

  1. Log in to CloudCADI using an Admin account.

    CloudCADI

  2. Click Onboarding (next to the Users tab) to begin onboarding a new cloud provider or data source.

    Onboarding tab

  3. On the Cloud account onboarding screen, click Manage Cloud Accounts to connect your AWS accounts.

    Cloud account onboarding

Step 2 - Add a New Data Source

  1. Click on the Add Data Source button at the top of the page.

    Add data source

    Auto Setup Requirement

    Auto Setup is supported only if the CloudCADI deployed account is:

    • The AWS management account, or
    • A member account configured as a delegated administrator.

Auto Setup

This section explains how an Admin can onboard AWS accounts into CloudCADI using the Auto Setup flow.

Step 1 - Grant Permissions and Define Cost Export Path

  1. Click Auto Setup and from the list of cloud providers, select AWS. Auto Setup

  2. Download the CloudFormation stack template.

    CloudFormation

  3. Deploy the stack by following the onboarding guide. This will create a role with the required permissions, including:

    • Organization-level read access
    • CloudFormation StackSet read and execute access
    Deployment Requirement

    Ensure the CloudFormation stack is created:

    • In the same AWS account where CloudCADI is deployed.
    • In the same region as the CloudCADI deployment.
  4. Open the AWS CloudFormation Console.

  5. Under Prepare template, select Choose an existing template.

  6. Under Template source, select Upload a template file.

  7. Upload the downloaded CloudFormation template file and click next. CloudFormation - template

  8. Under specify stack details. Enter stack name.

  9. For DeployedAccountType, select SELF if the CloudCADI deployed account is the AWS Organizations management account. Select DELEGATED_ADMIN if it is a member account configured as a delegated administrator.

    Enable Delegated Administrator

    Follow these steps to enable a delegated administrator in AWS Organizations:

    1. Sign in to the AWS Management Account and open AWS Organizations → Services.

    2. Find AWS CloudFormation StackSets and click Enable trusted access.

    3. Click Navigate to Console.

      image.png

    4. Under Delegated Administrators, click Register delegated administrator.

      image.png

    5. A popup will appear. Enter the Delegated Administrator Account ID and click Register Delegated Administrator.

    6. The member account can now perform the required actions.

      image.png

  10. Click Next. Specify-stack

  11. Under Configure stack options, scroll to the bottom, acknowledge the required capabilities by selecting the checkbox, and click Next. Configure stack

  12. Under Review and create, scroll down, verify all configuration details, and click Create stack.

    One-Time Setup
    • This CloudFormation stack deployment is a one-time setup.
    • CloudCADI automatically creates the required cross-account roles using StackSets when you select accounts from the UI.
  13. Enter the management account cost export path in the required format:

<bucket-name>/<prefix>/<export-name>

Deployment Requirement
  • The provided bucket must belong to the Management Account. If not, cost data will not be available for other accounts.
  • If you are using a cross-account bucket (for example, when the deployed account is a member account), ensure that the appropriate bucket policy is configured to allow access.
  1. Refer to the AWS Cost & Usage Data Export (FOCUS) documentation for detailed steps.

  2. Click Next. The cost export path and required permissions are validated, and the accounts are fetched and displayed in the UI.

Autosetup

Note

Entering the cost export path is required only the first time. For subsequent onboarding, accounts are fetched directly and you can select and onboard them without re-entering the cost export path.

Step 2 - Fetch and Select Accounts

  1. Once validation succeeds, all accounts in the same AWS Organization are fetched automatically. Select the accounts to onboard and click Onboard Selected.

    Select accounts

Step 3 - Track Onboarding Progress

  1. Go to the Onboarding Progress tab to view the onboarding status of each selected account.

Onboarding progress

  1. Once an account's state changes to Active and progress shows Completed, onboarding is complete and the account's cost and usage data will begin syncing into CloudCADI.

    Onboarding completed

Step 4 - Verify Data Source Creation

  1. Navigate to the Data Sources list tab and confirm the AWS account appears, with the provider shown as AWS and the configured Account name.

    Account Verification

  2. After successful onboarding, AWS cost and usage data becomes available across CloudCADI dashboards.

Update S3 Bucket Policy
  1. In the AWS Console, navigate to the S3 bucket configured for the cost export path.

    S3 buckets

  2. Go to the Permissions tab and click Edit.

    Bucket permissions

  3. Add the following statement to the existing bucket policy and click Save changes.

    {
    "Effect": "Allow",
    "Principal": {
    "AWS": "<ROLE_ARN>"
    },
    "Action": ["s3:GetObject", "s3:ListBucket"],
    "Resource": ["arn:aws:s3:::<BUCKET_NAME>", "arn:aws:s3:::<BUCKET_NAME>/*"]
    }
    tip
    • Replace <ROLE_ARN> with the Role ARN obtained during stack creation.
    • Replace <BUCKET_NAME> with your S3 bucket name.
    warning

    Do not remove existing statements in the bucket policy. Only add the above statement.

Manual Setup

This section explains how an Admin can onboard AWS accounts into CloudCADI using the Manual Setup flow.

Step 1 - Configure Data Source for Deployed Account

  1. In the Add Data Source tab, select Manual Setup.

    Manual Setup

  2. To complete onboarding for a CloudCADI-deployed account, enter the AWS Account ID, Account Name, and Cost export path.

    Account Details

  3. Click Next.

  4. CloudCADI validates the cost export path and required permissions.

  5. Refer to the AWS Cost & Usage Data Export (FOCUS) documentation for detailed steps.

  6. Once validation is complete, a confirmation page is displayed. Click Done to create the data source.

    Confirmation page

  7. You will be redirected to the Data Sources list page. Redirection

Step 2 - Configure Cross-Account Setup

  1. To onboard a cross-account setup, enter the AWS Account ID, Account Name, and Cost export path, then follow the stack deployment steps mentioned below.

  2. Click Download CloudFormation Template.

    Manual setup credentials

Step 3 - Deploy CloudFormation Stack

  1. After downloading the script, go to the AWS Console for the respective account, navigate to the CloudFormation service, and create a stack with new resources.

    Create Stack

  2. Select Choose an existing template.

  3. Select Upload a template file.

  4. Click Choose file and upload the downloaded script.

  5. Click Next.

    CloudFormation Template

  6. Enter the Stack name.

  7. Click Next.

    CloudFormation Template

  8. Enter the Tag key and Tag value.

  9. Click Next. The Review page appears.

Configure Stack

Capabilities

  1. Review the details and click Submit. It will take up to 5 minutes to finish the resource creation.

Confirmation

Step 4 - Complete Cross-Account Onboarding

  1. Once the stack has been created successfully, go to the Outputs tab and copy the Role ARN.

    Role ARN

  2. Paste the Role ARN in Enter the Role ARN to be assumed, obtained during stack creation, and click Confirm.

    Confirm Role ARN

  3. Once validation is complete. Verify the details and click Done to complete account creation.

    Confirmation

  4. Navigate back to the Data Sources list tab and confirm the AWS account appears, with the provider shown as AWS and the configured Account name.

    Data source list