Time to complete: ~10 minutes
Connect your AWS cost data
What Cloud Capital accesses
The Forecasting CloudFormation template creates an IAM role for the purposes below.The Forecasting role cannot purchase commitments and cannot create, modify, or delete your AWS infrastructure. Beyond reading data, its policy grants two Cost Explorer actions that start a job: a cost allocation tag backfill (
ce:StartCostAllocationTagBackfill), which asks Cost Explorer to backfill the activation history of your cost allocation tags, and a Savings Plans Purchase Analyzer analysis (ce:StartCommitmentPurchaseAnalysis). The analysis is stored in your account, where you can see it in Cost Explorer, and it counts toward your account’s AWS limits on stored analyses. No purchase is made.Before you begin
Optimization recommendations need setup on the AWS side. The Forecasting role can read
recommendations from AWS Compute Optimizer, Cost Optimization Hub, and Trusted Advisor, but
granting these permissions does not turn those services on:
- Compute Optimizer and Cost Optimization Hub each require opt-in, ideally for your whole organization from your management account. Until then they return no recommendations. When enabled organization-wide, these services return recommendations and findings for member accounts through the management account; Cloud Capital does not assume roles in those member accounts.
- Trusted Advisor’s full set of checks requires an AWS Business Support+, AWS Enterprise Support, or AWS Unified Operations plan on the account.
- Trusted Advisor access is broader than cost recommendations: the wildcard reads cover every check category, including security, fault tolerance, and service limits, and can also read notification settings, reports, Trusted Advisor Priority risks, and organization and account metadata.
Setup
1
Create a new Integration in Cloud Capital
From the main dashboard, navigate to Cost Allocation and click Connect Cloud Provider.
Then click Create New Integration, choose AWS, and give your integration a descriptive name (e.g., 

AWS).
2
Create a cost data export in AWS
This step walks you through creating a cost data export in the AWS Billing and Cost Management portal.
If you already have a daily CUR 2.0 export running with the settings below, you can use the existing bucket and skip ahead to the next step.
- In the AWS console, navigate to Billing and Cost Management
- Click Data Exports on the left, then click Create
- Select Standard data export
- Give the report a name (e.g.,
cloud-capital-cost-export) — you will enter this name in Cloud Capital
- Format: CUR 2.0 (default)
- Include resource IDs: No (leave unchecked)
- Split cost allocation data: No (leave unchecked)
- Time granularity: Hourly
- Column selection: keep the default
- Compression type and file format: Parquet - Parquet
- File versioning: Overwrite existing data export file
- Choose Configure → Create a bucket (recommended), or select an existing bucket
-
Add an S3 path prefix of
hourly-export
You will need the S3 destination (bucket name + path prefix + export name) in the next step. It is shown directly after creating the report — copy and paste it.
3
Add cost data export settings to Cloud Capital
Copy and paste the Bucket Name, Path Prefix, and Export Name from the previous step into the Integration settings in Cloud Capital.
4
Create the Forecasting IAM role
Under Create IAM Policy, click Run Cloud Formation Stack. Cloud Capital pre-populates the required parameters in the stack — you do not need to enter them manually. This creates an IAM role in your AWS Payer or Management account, scoped to your specific CUR bucket. The role cannot purchase commitments or create, modify, or delete your AWS infrastructure; its only non-read actions are the two Cost Explorer jobs described above, a cost allocation tag backfill and a Savings Plans Purchase Analyzer analysis.Once the stack completes, AWS provides a Role ARN. Enter this Role ARN in Cloud Capital.You can review the full policy: aws-cloudformation-forecasting.json
5
Test and enable your integration
Click Test Role to verify that Cloud Capital can access the bucket. If the connection is successful, your Integration status changes to Enabled. Save your integration to activate it.

AWS typically takes 24–48 hours to populate the Cost and Usage Report for the first time. After 24 hours, return to the Integration settings to verify that data is being imported before proceeding.
Commitment Optimization customers
If Cloud Capital will be managing AWS Savings Plans and Reserved Instances on your behalf, a second IAM role is required. See Commitment Purchasing Authorization for the full setup.
How the cross-account role works
The Forecasting role uses AWS’s standard cross-account access pattern with an ExternalId condition. Cloud Capital’s AWS account ID and your unique ExternalId are embedded in the role’s trust policy at setup time — meaning only Cloud Capital’s specific AWS account can assume the role, and only when presenting the correct ExternalId. This prevents confused deputy attacks. You can revoke the role at any time by deleting the CloudFormation stack (or the equivalent Terraform resources) in your AWS account, which immediately removes Cloud Capital’s access. See Disconnecting the integration below for step-by-step instructions. This is a well-established AWS pattern for granting third-party access. For more detail on how cross-account roles and ExternalId conditions work, see How to use an external ID when granting access to your AWS resources to a third party in the AWS documentation.Security and access summary
Security
For a full overview of how Cloud Capital handles data access, encryption, audit logging, and compliance, see the Security page.
Disconnecting the integration
If you no longer want Cloud Capital to access your AWS cost data, removing the Forecasting role’s IAM role is enough to immediately and completely cut off access. Cloud Capital’s AWS account has no other way to reach your CUR bucket or billing APIs — there’s no separate credential, API key, or token to revoke.1
Notify Cloud Capital
Let your Cloud Capital representative know you’re disconnecting the AWS integration. We’ll mark the integration inactive on our side and stop any scheduled data refreshes.
2
Remove the Forecasting IAM role
- Set up via CloudFormation
- Set up via Terraform
In the AWS account where you deployed the stack (your management or payer account):
- Open the CloudFormation console.
- Find the stack you created in Create the Forecasting IAM role — it created a
CrossAccountRoleresource. - Select the stack and click Delete.
3
Optional: stop or delete the Cost and Usage Report export
Removing the IAM role fully revokes Cloud Capital’s access on its own — this step is only needed if you also want AWS to stop generating the CUR export itself, or you want to remove the underlying S3 bucket.In the AWS console, go to Billing and Cost Management → Data Exports, select the export you created for Cloud Capital, and delete it (and the S3 bucket, if it isn’t used for anything else).
Nothing else needs to be rotated or revoked. The Forecasting role uses AWS’s cross-account trust pattern — no long-lived credentials, API keys, or tokens are ever issued to Cloud Capital — so deleting the IAM role is the entire revocation. See How the cross-account role works above for how the trust relationship is established in the first place.

