Native connector
AWS cost management from your own billing export
Costfluent reads AWS cost through a read-only IAM role in your account and a FOCUS 1.2 Data Export delivered to your own S3 bucket. The same cost basis then feeds cost reports, budgets, allocation, insights and savings.
How you connect
Four routes to the same read-only role
CloudFormation quick-create
The default route. AWS opens a CloudFormation page with every parameter filled in; when the stack finishes, the connection appears in Costfluent without anything to paste.
AWS CLI
Run the create-stack command Costfluent shows with credentials for the account you connect. It uses the same template and reports back the same way.
Terraform
The published costfluent/cost-access/aws module creates the role in your own Terraform and, where you name a bucket, the bucket and the export as well.
IAM console
Create the role yourself from the trust and permissions policies Costfluent shows, then enter its ARN and the export bucket.
What is read
Your cost data, from your account
FOCUS 1.2 Data Export
A daily export in the FOCUS format, delivered to a private S3 bucket you own. It carries amortized and list cost, charge categories, regions, resource IDs and tags.
Management and member accounts
Connect the management account of your AWS organization once: its export covers every member account. A member account another connection already covers is refused, so no cost is counted twice.
Cost Explorer until the first delivery
Until the export's first delivery arrives, and for any month it does not cover, Costfluent reads Cost Explorer and replaces those figures with the export's rows once they land.
What you grant
A read-only role you can delete at any time
- The role trusts one Costfluent principal, and only with the external ID issued to your organization. No access keys are exchanged.
- It may read Cost Explorer, list your organization's accounts, and read the export bucket. Nothing else in the account.
- Neither the role nor the export can change a resource or read workload content.
- Delete the stack, or run terraform destroy, and access ends. The export bucket stays in your account with your history.
Related pages
- Azure integration
A service principal with two read roles on the subscriptions you choose.
- Google Cloud integration
Read access to your detailed BigQuery billing export, without service-account keys.
- Kubernetes cluster agent
Node costs distributed across namespaces by an agent you install with Helm.
- All integrations
Every cost source Costfluent reads, with its status.
- Security and data access
Where Costfluent runs, the access each connector needs and how to revoke it.
From the handbook
- Billing data and standards
AWS Cost and Usage Report and Data Exports
- Tooling
AWS Cost Explorer and AWS Budgets
- AWS billing and pricing
Amazon EC2 pricing explained
- AWS billing and pricing
AWS Lambda pricing explained
- AWS billing and pricing
Amazon EKS, ECS and Fargate pricing
- AWS billing and pricing
Amazon EBS pricing explained
Start with your own AWS costs
Create a Free workspace and connect AWS when you are ready.
Permanent Free plan with no time limit