AWS CUR 2 Export Setup for Spotter
AWS CUR 2 Export Setup
This guide describes how to configure AWS Cost and Usage Report (CUR) 2.0 export for integration with Spotter.
1. Create Data Export
Navigate to Billing and Cost Management → Data exports → Create.
Export details
- Select type: Standard data export
- Export name:
spotter-cur-2
Data table content settings
- Select: CUR 2.0
- Additional export content:
- Include resource IDs
- Split cost allocation data
- Time granularity: Daily
Data export delivery options
- Compression type and file format: Parquet - Parquet
- File versioning: Overwrite existing data export file
Data export storage settings
- Use or create an S3 bucket to store exports.
- The S3 bucket policy must allow Spotter to fetch the data.
- After creating the export, edit the bucket policy to include the following blocks:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "AllowLambdaToRead",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::604877540157:role/aws-cur-ingestion"
},
"Action": [
"s3:ListBucket",
"s3:GetObject"
],
"Resource": [
"<s3-bucket-arn>",
"<s3-bucket-arn>/*"
]
},
{
"Sid": "AllowLinkedAccountsToReadAndWrite",
"Effect": "Allow",
"Principal": {
"AWS": ["arn:aws:iam::604877540157:role/Cloud2Admin"]
},
"Action": [
"s3:ListBucket",
"s3:GetObject",
"s3:PutObject",
"s3:DeleteObject"
],
"Resource": [
"<s3-bucket-arn>",
"<s3-bucket-arn>/*"
]
}
]
}
- S3 path prefix: e.g.
spotter
2. Verify Export
- After creation, confirm exports appear in the configured bucket.
- Expected path format:
s3://<bucket-name>/<prefix>/<export-name>/data/BILLING_PERIOD=YYYY-MM/ - Notes:
- It may take up to 24 hours for data to appear.
- If exports do not appear, ensure AWS permissions to write into the bucket were not removed when adding Spotter read permissions.
3. Deliver S3 URI to Spotter Team
- Once exports are working, send the S3 bucket URI to Team Spotter.
- Example URI:
s3://<bucket-name>/<prefix>/<export-name>