-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Adding AWS Cloud Cost Management Instructions for MSP Partners #33259
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.
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
base: master
Are you sure you want to change the base?
Conversation
Preview links (active after the
|
|
Opened DOCS-12876 to assign a Docs writer and follow up with editorial review. |
rtrieu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @patrickywl, I've left a ton of feedback but it's mostly around formatting. Thanks so much for this PR! Aside from my suggestions, some general notes:
- lots of terms such as member account should be in lowercase unless they are product/feature names
- I think all the content under line 139 (Configure the Cost and Usage Report settings in Datadog) can be consolidated into one step. for ex:
- the last image doesn't show the "Activate now button" (but the previous one does), so not sure what we're trying to show there. i would remove it.
happy to work with you on this further!
| subcategory: 'Cloud Cost Management' | ||
| --- | ||
|
|
||
| This section provides Cloud Cost Management guidance specifically for **Managed Service Provider (MSP) partners** who need to enable secure, customer-facing cost visibility using Datadog. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| This section provides Cloud Cost Management guidance specifically for **Managed Service Provider (MSP) partners** who need to enable secure, customer-facing cost visibility using Datadog. | |
| As a **Managed Service Provider MSP) partner**, you can use Cloud Cost Management to provide your customers with secure, actionable insights into their cloud spending. |
| This section provides Cloud Cost Management guidance specifically for **Managed Service Provider (MSP) partners** who need to enable secure, customer-facing cost visibility using Datadog. | ||
|
|
||
| {{< whatsnext desc="To start managing cloud costs with Cloud Cost Management, see the following documentation.">}} | ||
| {{< nextlink href="/partners/cloud_cost_management/aws">}}<u>AWS</u>: Configure Cloud Cost Management for AWS bill.{{< /nextlink >}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| {{< nextlink href="/partners/cloud_cost_management/aws">}}<u>AWS</u>: Configure Cloud Cost Management for AWS bill.{{< /nextlink >}} | |
| {{< nextlink href="/partners/cloud_cost_management/aws">}}<u>AWS</u>: Set up AWS cost visibility for your customers.{{< /nextlink >}} |
| - link: "https://www.datadoghq.com/blog/total-cost-of-service-ownership-ccm/" | ||
| tag: "Blog" | ||
| text: "Quickly and comprehensively analyze the cloud and SaaS costs behind your services" | ||
| text: "Learn about Tags in Cloud Cost Management" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is an orphan line
| text: "Learn about Tags in Cloud Cost Management" |
| text: "Understand your Kubernetes and ECS spend with Datadog Cloud Cost Management" | ||
| - link: "https://www.datadoghq.com/blog/google-cloud-cost-management/" | ||
| tag: "Blog" | ||
| text: "Empower engineers to take ownership of Google Cloud costs with Datadog" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this relevant?
| - link: "https://www.datadoghq.com/blog/cloud-cost-management-saved-millions/" | ||
| tag: "Blog" | ||
| text: "How we saved $1.5 million per year with Cloud Cost Management" | ||
| - link: "https://www.datadoghq.com/blog/cloud-cost-management-oci/" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this relevant?
|
|
||
| [1]: /cloud_cost_management/setup/aws/ | ||
| [2]: /cloud_cost_management/setup/aws/?tab=manual#prerequisite-generate-a-cost-and-usage-report | ||
| [3]: /getting_started/integrations/aws/#setup |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| [3]: /getting_started/integrations/aws/#setup |
| [1]: /cloud_cost_management/setup/aws/ | ||
| [2]: /cloud_cost_management/setup/aws/?tab=manual#prerequisite-generate-a-cost-and-usage-report | ||
| [3]: /getting_started/integrations/aws/#setup | ||
| [4]: https://app.datadoghq.com/cost/settings/accounts |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| [4]: https://app.datadoghq.com/cost/settings/accounts |
| [2]: /cloud_cost_management/setup/aws/?tab=manual#prerequisite-generate-a-cost-and-usage-report | ||
| [3]: /getting_started/integrations/aws/#setup | ||
| [4]: https://app.datadoghq.com/cost/settings/accounts | ||
| [11]: https://docs.aws.amazon.com/billingconductor/latest/userguide/what-is-billingconductor.html |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| [11]: https://docs.aws.amazon.com/billingconductor/latest/userguide/what-is-billingconductor.html |
| [3]: /getting_started/integrations/aws/#setup | ||
| [4]: https://app.datadoghq.com/cost/settings/accounts | ||
| [11]: https://docs.aws.amazon.com/billingconductor/latest/userguide/what-is-billingconductor.html | ||
| [12]: https://docs.aws.amazon.com/cur/latest/userguide/cur-data-view.html |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| [12]: https://docs.aws.amazon.com/cur/latest/userguide/cur-data-view.html |
| [4]: https://app.datadoghq.com/cost/settings/accounts | ||
| [11]: https://docs.aws.amazon.com/billingconductor/latest/userguide/what-is-billingconductor.html | ||
| [12]: https://docs.aws.amazon.com/cur/latest/userguide/cur-data-view.html | ||
| [13]: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-console-create-stack.html |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| [13]: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-console-create-stack.html |
|
Hi @rtrieu, thank you so much for the thorough and detailed review. I agree with your suggestions. |


What does this PR do? What is the motivation?
This PR introduces MSP-specific AWS Cloud Cost Management setup documentation under the Partners section.
For background and full context, see the following documents:
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes