Skip to content

Amazon Web Services (AWS)

Connect one or more AWS accounts or an AWS Organization to bring billing, resource inventory, and commitment data into CloudVerse AI.

What you get

  • Billing data from AWS Cost and Usage Report (CUR)
  • Full resource inventory across regions and services
  • Reserved Instance and Savings Plan coverage and recommendations
  • Anomaly detection and budget tracking per account or organization

Prerequisites

  • AWS account with administrator access (or delegated billing access)
  • An S3 bucket for CUR export, or permission to create one
  • IAM role that CloudVerse can assume for read access

Connect AWS

  1. Go to Settings > Integrations.
  2. Select Amazon Web Services.
  3. Enter a connection name — for example, aws-production.
  4. Choose your authentication method:
    • Token — provide an Access Key ID and Secret Access Key.
    • CLI Console — follow the in-app guided flow to set up an IAM role via AWS Console.
  5. Complete the Billing Setup step: configure or confirm your CUR export to S3.
  6. Choose the Discovery scope — individual account or full AWS Organization.
  7. Finish the flow and wait for initial data ingestion.

Verify the connection

  1. Go to Settings > Integrations and open the AWS connection detail page.
  2. Confirm that billing and discovery status indicators are green.
  3. Open Cost Management > Cost Explorer, filter by Provider: AWS, and check that data appears.
  4. Open Cloud Infrastructure > Resources and filter by your AWS account to verify inventory.

Permissions required

CloudVerse requires an IAM role with the following minimum permissions:

  • ce:GetCostAndUsage and related Cost Explorer read permissions
  • s3:GetObject and s3:ListBucket on the CUR export bucket
  • ec2:Describe*, rds:Describe*, and service-specific read permissions for inventory discovery

For the full recommended policy, refer to the in-app IAM policy template provided during setup.

Connect multiple AWS accounts

To connect additional accounts:

  • Repeat the setup flow for each account, or
  • Connect at the AWS Organization level during initial setup to pull all member accounts automatically.

Best practices

  • Use the CLI Console flow to create a least-privilege IAM role rather than long-lived access keys.
  • Enable CUR at the management account level if using AWS Organizations.
  • Include resource IDs and tags in your CUR export for accurate inventory mapping.
  • Rotate access keys on schedule and update credentials in CloudVerse immediately after.

Troubleshooting

  • No billing data after 24 hours — Check that the CUR export is configured in AWS and that the S3 bucket has the correct permissions.
  • Missing resources — Verify that the IAM role has the required Describe* permissions for the services you expect to see.
  • Status shows error — Open the integration detail page; the error message identifies the failing step.

See Integration setup issues for more help.