Skip to content

CCC-1910: Add documentation for using AWS CUR 2.0 in CCM #38213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
t-omalley wants to merge 4 commits into
base: master
Choose a base branch
from
Open

CCC-1910: Add documentation for using AWS CUR 2.0 in CCM #38213

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
7fe0dd9
updating AWS documentation with CUR 2.0 information
t-omalley Jul 16, 2026
366a88c
Update in 'Cost and Usage Report columns' section
t-omalley Jul 16, 2026
6552471
Remove extra empty line
t-omalley Jul 16, 2026
ae1ab42
Removing duplicate CUR 2.0 policy
t-omalley Jul 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 26 additions & 8 deletions content/en/cloud_cost_management/setup/aws.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,8 +59,15 @@

### Configure the Cost and Usage Report settings

Enter the following details for your Cost and Usage Report:
If using an existing Cost and Usage Report 2.0 and bucket:

* Select your report from the {{< ui >}}Data Export{{< /ui >}} field and continue to the next step.

{{< img src="cloud_cost/setup/aws_data_export_selector.png" alt="CCM Setup Page with Create Cost and Usage Report and Create S3 Bucket unselected, showing the Data Export selector used to select an existing export" style="width:100%" >}}

Otherwise, enter the following details for your Cost and Usage Report:

* {{< ui >}}Report Content{{< /ui >}}: The version of your Cost and Usage Report (Legacy CUR or CUR 2.0).
* {{< ui >}}Bucket Name{{< /ui >}}: The S3 bucket name where the report files are stored.
* {{< ui >}}Bucket Region{{< /ui >}}: The AWS [region code][100] of the region containing your S3 bucket. For example, `us-east-1`.
* {{< ui >}}Export Path Prefix{{< /ui >}}: The S3 path prefix where report files are stored.
Expand Down Expand Up @@ -92,8 +99,15 @@

### Configure the Cost and Usage Report settings

Enter the following details for your Cost and Usage Report:
If using an existing Cost and Usage Report 2.0 and bucket:

* Select your report from the {{< ui >}}Data Export{{< /ui >}} field and continue to the next step.

{{< img src="cloud_cost/setup/aws_data_export_selector.png" alt="CCM Setup Page with Create Cost and Usage Report and Create S3 Bucket unselected, showing the Data Export selector used to select an existing export" style="width:100%" >}}

Otherwise, enter the following details for your Cost and Usage Report:

* {{< ui >}}Report Content{{< /ui >}}: The version of your Cost and Usage Report (Legacy CUR or CUR 2.0).
* {{< ui >}}Bucket Name{{< /ui >}}: The S3 bucket name where the report files are stored.
* {{< ui >}}Bucket Region{{< /ui >}}: The AWS [region code][100] of the region containing your S3 bucket. For example, `us-east-1`.
* {{< ui >}}Export Path Prefix{{< /ui >}}: The S3 path prefix where report files are stored.
Expand All @@ -119,13 +133,11 @@

### Prerequisite: generate a Cost and Usage Report

[Create a Legacy Cost and Usage Report][201] in AWS under the {{< ui >}}Data Exports{{< /ui >}} section.

Select the Export type {{< ui >}}Legacy CUR export{{< /ui >}}.
Create either a [Cost and Usage Report 2.0][202] or a [Legacy Cost and Usage Report][201] in AWS under the {{< ui >}}Data Exports{{< /ui >}} section.

Select the following content options:

* Export type: {{< ui >}}Legacy CUR export{{< /ui >}}
* Export type: {{< ui >}}CUR 2.0 export{{< /ui >}} or {{< ui >}}Legacy CUR export{{< /ui >}}
* {{< ui >}}Include resource IDs{{< /ui >}}
* {{< ui >}}Split cost allocation data{{< /ui >}} (Enables ECS Cost Allocation. You must also opt in to [AWS Split Cost Allocation][210] in Cost Explorer preferences).
* {{< ui >}}Refresh automatically{{< /ui >}}

@kaankoseler kaankoseler Jul 16, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's add wording here for this checkbox:

Image 
Enable IAM Principal Allocation Data for granular user-level IAM Principal Bedrock Cost Allocation.

@t-omalley t-omalley Jul 16, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I think this specific spot is just in the manual tab, but is this information relevant to all setup methods? We could add a note outside of the setup tabs in that case

@kaankoseler kaankoseler Jul 16, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also wording for this checkbox:

Image

Although this is pending some input from the commitments team, so maybe a fast follow

@t-omalley t-omalley Jul 16, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, are we waiting on them for the copy here?

Expand All @@ -136,9 +148,11 @@
* Report versioning: {{< ui >}}Create new report version{{< /ui >}}
* Compression type: {{< ui >}}GZIP{{< /ui >}} or {{< ui >}}Parquet{{< /ui >}}

**Note**: Datadog only supports one Cost and Usage Report per member account.

### Locate the Cost and Usage Report

If you have navigated away from the report that you created in the prerequisites section, follow AWS documentation to [view your Data Exports][204]. Select the legacy CUR export that you created, then select {{< ui >}}Edit{{< /ui >}} to see the details of the export.
If you have navigated away from the report that you created in the prerequisites section, follow AWS documentation to [view your Data Exports][204]. Select the CUR export that you created, then select {{< ui >}}Edit{{< /ui >}} to see the details of the export.

To enable Datadog to locate the Cost and Usage Report, complete the fields with their corresponding details:

Expand All @@ -148,7 +162,7 @@
* **Note:** The following prefix formats are not supported: empty, starting with `/` (such as `/` or `/cost`), or ending with `/` (such as `cost/`). Prefixes containing `/` in the middle are supported (such as `cost/hourly`).
* {{< ui >}}Export Name{{< /ui >}}: This is the Export name in the Export name section.

**Note**: Datadog only supports legacy Cost and Usage Reports (CURs) generated by AWS. Do not modify or move the files generated by AWS, or attempt to provide access to files generated by a third party.
**Note**: Datadog only supports Cost and Usage Reports (CURs) generated by AWS. Do not modify or move the files generated by AWS, or attempt to provide access to files generated by a third party.

{{< site-region region="gov,gov2" >}}
<div class="alert alert-danger">The AWS Cost and Usage Reports endpoint is used to validate the above fields against the CUR export in your S3 bucket. This endpoint is not FIPS validated.</div>
Expand Down Expand Up @@ -222,6 +236,7 @@
**Note**: It may take between 48 and 72 hours for all available data to populate in your Datadog organization after a complete Cost and Usage Report is generated. If 72 hours have passed and the data has still not yet populated, contact [Datadog Support][18].

[201]: https://docs.aws.amazon.com/cur/latest/userguide/dataexports-create-legacy.html
[202]: https://docs.aws.amazon.com/cur/latest/userguide/dataexports-create-standard.html
[204]: https://docs.aws.amazon.com/cur/latest/userguide/dataexports-view.html
[205]: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create-console.html
[210]: https://docs.aws.amazon.com/cur/latest/userguide/enabling-split-cost-allocation-data.html
Expand Down Expand Up @@ -363,6 +378,8 @@
|product/region|us-east-1|product/region:us-east-1|
|product/usagetype|DataTransfer-Regional-Bytes|product/usagetype:DataTransfer-Regional-Bytes|

Refer to the [AWS CUR 2.0 documentation][33] to learn more about additional columns in the CUR 2.0 export.

Check warning on line 381 in content/en/cloud_cost_management/setup/aws.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.words_case_insensitive 

Use 'see', 'read', or 'follow' instead of 'Refer to'.

### AWS resource tags

[AWS resource tags][12] are user-defined tags that appear in the AWS console when viewing a particular resource, such as an EC2 instance or S3 bucket.
Expand Down Expand Up @@ -525,3 +542,4 @@
[30]: /cloud_cost_management/recommendations/
[31]: https://docs.aws.amazon.com/cost-management/latest/userguide/cost-optimization-hub.html
[32]: /integrations/amazon_web_services/
[33]: https://docs.aws.amazon.com/cur/latest/userguide/table-dictionary-cur2.html
Binary file modified static/images/cloud_cost/setup/aws_cloudformation_setup.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added static/images/cloud_cost/setup/aws_data_export_selector.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified static/images/cloud_cost/setup/aws_manual_setup.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified static/images/cloud_cost/setup/aws_terraform_setup.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading