Skip to main content
Open Costory and go to Billing > Import new billing datasource > AWS. The stepper guides you through each field. The steps below explain how to prepare your AWS account.You can use CloudFormation or set things up manually. Both paths produce the same result: an S3 bucket with data and an IAM role that Costory can assume.Option A: CloudFormation (recommended)
  1. Open the CloudFormation template in us-east-1.
  2. Deploy the stack and note the Bucket Name, Role ARN, and Prefix from the stack outputs.
Option B: Manual
  1. Create a CUR 2.0 data export in the AWS Billing console (Parquet format, overwrite enabled). Use hourly granularity if you run EKS or ECS, daily otherwise.
  2. Create an S3 read-only IAM policy scoped to the export bucket.
  3. Create a web identity IAM role trusted by Costory’s GCP service account.
Connect in Costory
  1. Go to Billing > Import new billing datasource > AWS.
  2. Enter the S3 bucket name, Role ARN, and Prefix.
  3. If you run EKS or ECS, enable and activate the relevant cost allocation tags (aws:eks:*, aws:ecs:*). This gives you pod-level (EKS) and job-level (ECS) cost granularity. See Kubernetes cost visibility for details.
Cost allocation tags: Activate as many cost allocation tags as you can in the AWS Billing console. Costory’s Feature Engineering automatically detects and merges meaningful tags so you can filter by team, environment, project, etc.
The first AWS export can take up to 12 hours. Costory sends you an email when data is received. Backfill covers up to 12 months via aws:createdBy tag backfill. For longer periods, open an AWS Support request.
Costory datasource successfully connected
Last modified on March 18, 2026