AWS Cloud Financial Management
Author: Scott Ma
Scott Ma is a Senior Technical Account Manager (TAM) at Amazon Web Services who specializes in Security and Generative AI. He is passionate about helping customers solve real-world challenges by architecting secure, scalable, and innovative solutions on AWS. Outside of work, Scott enjoys exploring the latest in AI and sharing knowledge with the builder community.
Automating filtered Cost and Usage Report exports with AWS Data Exports
AWS Data Exports lets you select which columns to include in your AWS Cost and Usage Reports (CUR 2.0) export. But filtering down rows to specific accounts or services still required post-processing. Whether you need to share cost data with a partner, isolate a program’s spend, or meet an audit scope, teams often build downstream pipelines with AWS Lambda, AWS Glue, or Amazon Athena. AWS Data Exports supports SQL-based row filtering at the source. Each destination receives a pre-filtered dataset including only the rows that match your criteria with no post-processing step required. In this post, you’ll learn how to filter CUR 2.0 data at the source using AWS Data Exports SQL query capabilities, so you get the data you need.