CCC-1910: Add documentation for using AWS CUR 2.0 in CCM#38213
Open
t-omalley wants to merge 2 commits into
Open
CCC-1910: Add documentation for using AWS CUR 2.0 in CCM#38213t-omalley wants to merge 2 commits into
t-omalley wants to merge 2 commits into
Conversation
Contributor
Preview links (active after the
|
hinosxz
reviewed
Jul 16, 2026
|
|
||
| [Create a policy][205] in AWS to ensure Datadog has permissions to access the CUR and the S3 bucket it is stored in. Use the following JSON: | ||
|
|
||
| {{< ui >}}Policy for CUR 2.0{{< /ui >}}: |
Contributor
There was a problem hiding this comment.
This one seems to be the same as the one below and supports both the legacy and the new data exports API so I think we can remove the other one.
joepeeples
approved these changes
Jul 16, 2026
joepeeples
left a comment
joepeeples
left a comment
Contributor
There was a problem hiding this comment.
Approved with 1 non-blocking edit suggestion, thanks!
Comment on lines
+68
to
+71
| 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). |
Contributor
There was a problem hiding this comment.
Removing extra empty line:
Suggested change
| 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). | |
| 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). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Jira ticket
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Additional notes