Docs / Data sources / AWS Cost and Usage Reports

AWS Cost and Usage Reports

Business software

Built when you ask for it

Sync AWS Cost and Usage Reports data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The AWS Cost and Usage Reports connector syncs your cloud spend data into analytics-ready tables in your data warehouse. Pull cost reports, usage line items, and savings plans from the AWS CUR API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Cost reports
  • Usage line items
  • Savings plans

How it gets built

  1. Choose AWS Cost and Usage Reports when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads AWS Cost and Usage Reports's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against AWS Cost and Usage Reports itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

AWS IAM credentials (SigV4 signing). Attach an IAM policy granting CUR permissions to a user or role; requests are signed with that identity's credentials.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a AWS Cost and Usage Reports connector?
Not as a finished connector yet. Ingest builds it from AWS Cost and Usage Reports's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can AWS Cost and Usage Reports data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

AWS Cost and Usage Reports API documentation: https://docs.aws.amazon.com/cur/latest/userguide/what-is-cur.html

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request AWS Cost and Usage Reports