CCC-1910: Add documentation for using AWS CUR 2.0 in CCM#38213
CCC-1910: Add documentation for using AWS CUR 2.0 in CCM#38213t-omalley wants to merge 4 commits into
Conversation
Preview links (active after the
|
|
|
||
| [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 >}}: |
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
left a comment
joepeeples
left a comment
There was a problem hiding this comment.
Approved with 1 non-blocking edit suggestion, thanks!
Co-authored-by: Joe Peeples <joe.peeples@datadoghq.com>
cf6d39a to
ae1ab42
Compare
|
@joepeeples Is there a best way to add a little more spacing between the text and image? This text / image combo appears in both the CloudFormation and Terraform tabs 
|
kaankoseler
left a comment
kaankoseler
left a comment
There was a problem hiding this comment.
I think we'll still support legacy CUR 1.0 setup, right?
At least the way the PR looks at the moment it seems to be overwriting some of the legacy setup, unless I'm reading incorrectly.
| * 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 >}} |
There was a problem hiding this comment.
Let's add wording here for this checkbox:
Enable IAM Principal Allocation Data for granular user-level IAM Principal Bedrock Cost Allocation.
There was a problem hiding this comment.
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
| * 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 >}} |
There was a problem hiding this comment.
also wording for this checkbox:
Although this is pending some input from the commitments team, so maybe a fast follow
There was a problem hiding this comment.
Ok, are we waiting on them for the copy here?
@kaankoseler Is there a specific spot that's confusing? I tried to update the existing legacy setup docs to make sense for both but let me know if that isn't clear |
4 participants
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