From f0853a930b1c44a9e816663b7041bcc2c55913e1 Mon Sep 17 00:00:00 2001 From: "zeina.gebran" Date: Fri, 7 Aug 2026 14:41:25 +0200 Subject: [PATCH 01/10] [CCR-3653] Add Automated Notifications page and update Remediation automation docs Splits notification rules into their own page (automated_notifications.md), matching the Notification/Remediation tabs in the Automations UI, and updates the Cost Optimization Automation page with the current recommendation type coverage, prerequisites, and setup steps. --- hugo/config/_default/menus/main.en.yaml | 7 ++- .../recommendations/_index.md | 2 + .../automated_notifications.md | 55 +++++++++++++++++ .../cost_optimization_automation.md | 59 ++++++++++++------- 4 files changed, 102 insertions(+), 21 deletions(-) create mode 100644 hugo/content/en/cloud_cost_management/recommendations/automated_notifications.md diff --git a/hugo/config/_default/menus/main.en.yaml b/hugo/config/_default/menus/main.en.yaml index 6b4e4bc7782..68e396a3f77 100644 --- a/hugo/config/_default/menus/main.en.yaml +++ b/hugo/config/_default/menus/main.en.yaml @@ -4227,11 +4227,16 @@ menu: parent: cloud_cost_recommendations identifier: cloud_cost_optimization_automation weight: 700 + - name: Automated Notifications + url: cloud_cost_management/recommendations/automated_notifications + parent: cloud_cost_recommendations + identifier: cloud_cost_automated_notifications + weight: 701 - name: Custom Recommendations url: cloud_cost_management/recommendations/custom_recommendations parent: cloud_cost_recommendations identifier: cloud_cost_custom_recommendations - weight: 701 + weight: 702 - name: Planning url: cloud_cost_management/planning parent: cloud_cost diff --git a/hugo/content/en/cloud_cost_management/recommendations/_index.md b/hugo/content/en/cloud_cost_management/recommendations/_index.md index ba78e2e79ab..73c326353de 100644 --- a/hugo/content/en/cloud_cost_management/recommendations/_index.md +++ b/hugo/content/en/cloud_cost_management/recommendations/_index.md @@ -801,6 +801,7 @@ You can act on recommendations to save money and optimize costs. Cloud Cost Reco - **[Bits Code][14] code fixes**: Code fixes are available for applicable S3 and DynamoDB recommendations, as well as the Downsize Kubernetes Deployment recommendation. In these situations, Bits Code creates production-ready pull requests to implement cloud resource changes and cost optimizations in Terraform or Helm charts, respectively. [Set up Bits Code][13] to use this feature. - **1-click Workflow Automation actions**: Actions are available for a limited set of recommendations, allowing users to execute suggested actions, such as clicking {{< ui >}}Delete EBS Volume{{< /ui >}}, directly within Cloud Cost Management. - **[Cost Optimization Automation][15]**: Set up automations that act on recommendations continuously on a recurring schedule. Automations are scoped to specific accounts, regions, and tags and include safeguards such as pre-action snapshots and optional human approval through Slack or Microsoft Teams. +- **[Automated Notifications][19]**: Set up notification rules that send a recurring Slack summary of matching recommendations, without taking any action. - **Datadog Case Management**: Users can go to the recommendation side panel and click {{< ui >}}Create Case{{< /ui >}} to generate a case to manage and take action on recommendations. - **Dismiss**: Use {{< ui >}}Dismiss{{< /ui >}} in the recommendation side panel to hide a recommendation for a chosen time frame and provide a reason. Dismissed recommendations move to the {{< ui >}}Dismissed{{< /ui >}} tab. @@ -827,6 +828,7 @@ You can act on recommendations to save money and optimize costs. Cloud Cost Reco [13]: /bits_ai/bits_code/setup [14]: /bits_ai/bits_code/ [15]: /cloud_cost_management/recommendations/cost_optimization_automation/ +[19]: /cloud_cost_management/recommendations/automated_notifications/ [16]: /mcp_server/tools/#cost_recommendations [17]: /cloud_cost_management/setup/saas_costs/?tab=openai#configure-your-saas-accounts [18]: /cloud_cost_management/setup/saas_costs/?tab=anthropic#configure-your-saas-accounts diff --git a/hugo/content/en/cloud_cost_management/recommendations/automated_notifications.md b/hugo/content/en/cloud_cost_management/recommendations/automated_notifications.md new file mode 100644 index 00000000000..d4d24e637f5 --- /dev/null +++ b/hugo/content/en/cloud_cost_management/recommendations/automated_notifications.md @@ -0,0 +1,55 @@ +--- +title: Automated Notifications +description: Set up notification rules that send a recurring Slack summary of Cloud Cost Recommendations matching a scope you define. +further_reading: +- link: "/cloud_cost_management/" + tag: "Documentation" + text: "Cloud Cost Management" +- link: "/cloud_cost_management/recommendations/" + tag: "Documentation" + text: "Cloud Cost Recommendations" +- link: "/cloud_cost_management/recommendations/cost_optimization_automation/" + tag: "Documentation" + text: "Cost Optimization Automations" + +--- + +## Overview + +A notification rule sends a recurring Slack summary of [Cloud Cost Recommendations][1] matching a scope you define, without taking any action on your resources. Use a notification rule when you want visibility into new savings opportunities without configuring Datadog to make changes automatically. + +Notification rules are different from [Cost Optimization Automations][2], which act on recommendations directly on a recurring schedule. + +## Prerequisites + +- A Slack connection. See [Slack integration][3]. + +## Set up a notification rule + +To set up a notification rule: + +1. Navigate to [{{< ui >}}Cloud Cost{{< /ui >}} > {{< ui >}}Optimize{{< /ui >}} > {{< ui >}}Automations{{< /ui >}}][4]. +1. Select the {{< ui >}}Notification{{< /ui >}} tab. +1. In the {{< ui >}}Define scope{{< /ui >}} section, enter tags to restrict the notification to resources matching those tags. Leave this blank to include all resources. +1. In the {{< ui >}}Set schedule{{< /ui >}} section, select the notification frequency, execution day, execution time, and timezone. +1. In the destination section, select a Slack workspace connection and channel. +1. Enter a name for the notification rule. +1. Use the {{< ui >}}Notification enabled{{< /ui >}} toggle to control whether the rule is active. +1. Click **Save**. + +## Manage notification rules + +The {{< ui >}}Notification{{< /ui >}} tab lists every notification rule in your organization. From this page you can: + +- Toggle a rule on or off without deleting it +- Edit a rule's scope, schedule, destination, or name +- Delete a rule + +## Further reading + +{{< partial name="whats-next/whats-next.html" >}} + +[1]: /cloud_cost_management/recommendations/ +[2]: /cloud_cost_management/recommendations/cost_optimization_automation/ +[3]: /integrations/slack/ +[4]: https://app.datadoghq.com/cost/optimize/automations diff --git a/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md b/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md index c5489d4d12d..863de68b38c 100644 --- a/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md +++ b/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md @@ -1,5 +1,5 @@ --- -title: Cost Optimization Automation +title: Cost Optimization Automations description: Set up automations that continuously act on Cloud Cost Recommendations to clean up unused or wasteful cloud resources on a recurring schedule. further_reading: - link: "/cloud_cost_management/" @@ -8,6 +8,9 @@ further_reading: - link: "/cloud_cost_management/recommendations/" tag: "Documentation" text: "Cloud Cost Recommendations" +- link: "/cloud_cost_management/recommendations/automated_notifications/" + tag: "Documentation" + text: "Automated Notifications" - link: "/actions/workflows/" tag: "Documentation" text: "Workflow Automation" @@ -16,39 +19,53 @@ further_reading: ## Overview -Cost Optimization Automation lets you continuously act on [Cloud Cost Recommendations][1] without manual cleanup. You define an **automation**, scope it to the accounts, regions, and resources you want, and Datadog executes the recommended action on a recurring schedule. Each run can require human approval in Slack or Microsoft Teams before Datadog makes any changes, so your team stays in control of every change. +The {{< ui >}}Remediation{{< /ui >}} tab lets you continuously act on [Cloud Cost Recommendations][1] without manual cleanup. You define an **automation**, scope it to the accounts, regions, and resources you want, and Datadog executes the recommended action on a recurring schedule. Each run can require human approval in Slack or Microsoft Teams before Datadog makes any changes, so your team stays in control of every change. Each automation targets a single recommendation type and includes the following: - A schedule (weekly, biweekly, every 30 days, or every 90 days) -- A scope (AWS account, region, tags, and a maximum number of resources per run) +- A scope (account, region, tags, and a maximum number of resources per run) - Safeguards specific to the recommendation type (for example, a pre-deletion snapshot) - An optional human approval step routed through Slack or Microsoft Teams Recommendations acted on by an automation move to {{< ui >}}Completed{{< /ui >}} automatically and contribute to realized savings on the [Cloud Cost Recommendations][1] page. -Cost Optimization Automation is different from the 1-click Workflow Automation actions described in [Recommendation action-taking][2]. 1-click actions execute a single change on demand from the recommendation side panel. Automations execute on a recurring schedule and act on every matching resource in scope. +Remediation automations are different from the 1-click Workflow Automation actions described in [Recommendation action-taking][2]. 1-click actions execute a single change on demand from the recommendation side panel. Automations execute on a recurring schedule and act on every matching resource in scope. -**Note**: Cost Optimization Automation uses Datadog Workflows and incurs additional costs. For detailed pricing information, see the [Workflow Automation pricing page][3]. +Remediation automations are also different from [Automated Notifications][8], which send a recurring Slack summary of matching recommendations but don't take any action. -## Supported recommendation types +**Note**: Remediation automations use Datadog Workflows and incur additional costs. For detailed pricing information, see the [Workflow Automation pricing page][3]. -Cost Optimization Automation supports the following AWS recommendation types: +## Supported recommendation types -| Recommendation type | Built-in safeguards | -|---------------------|---------------------| -| Delete unattached EBS volume | An EBS snapshot is taken before each volume is deleted. | -| Transition S3 Standard objects to Amazon S3 Intelligent-Tiering | Reversible. The lifecycle configuration can be removed at any time. | -| Delete unused RDS instance | A final RDS snapshot is taken before each instance is deleted. | -| Delete extra on-demand backups (DynamoDB) | The two most recent backups are preserved on every run. | -| Set CloudWatch logs retention policy | Reversible. The retention period can be adjusted or removed at any time. | -| Delete old EBS snapshots | Snapshots referenced by an AMI are skipped. | +The {{< ui >}}Remediation{{< /ui >}} tab supports the following recommendation types: + +| Provider | Recommendation type | Built-in safeguards | +|----------|---------------------|---------------------| +| AWS | Delete unattached EBS volume | Optional: takes an EBS snapshot before each volume is deleted. | +| AWS | Migrate EBS volume from gp2 to gp3 | Reversible, in-place migration with no data loss. | +| AWS | Delete unused EBS snapshots | Snapshots referenced by an AMI are skipped. | +| AWS | Delete extra on-demand backups (DynamoDB) | The two most recent backups are preserved on every run. | +| AWS | Migrate DynamoDB table to Infrequent Access table class | Reversible. The table class can be changed back at any time. | +| AWS | Delete unused DynamoDB table | A backup is taken before each table is deleted. | +| AWS | Set CloudWatch logs retention policy | Reversible. The retention period can be adjusted or removed at any time. | +| AWS | Delete unused RDS instance | A final RDS snapshot is taken before each instance is deleted. | +| AWS | Delete unused NAT gateway | None. Deletion is irreversible. | +| AWS | Transition S3 Standard objects to Amazon S3 Intelligent-Tiering | Existing lifecycle rules are preserved rather than overwritten. | +| AWS | Delete unused EC2 instance | Optional: creates an AMI before each instance is deleted. | +| AWS | Delete unused Redshift cluster | A final snapshot is taken before each cluster is deleted. | +| GCP | Delete unattached Compute Engine disk | Optional: takes a snapshot before each disk is deleted. | +| GCP | Enable Autoclass on a Cloud Storage bucket | Reversible. Autoclass can be disabled at any time. | +| Azure | Delete unattached managed disk | Optional: takes a snapshot before each disk is deleted. | +| Azure | Delete unused SQL database | None. Deletion is irreversible. | + +Safeguards marked "Optional" are enabled by default and can be turned off in the automation form. All other listed safeguards are always applied and can't be disabled. ## Prerequisites -- An AWS account configured with [Cloud Cost Recommendations][4] and actively generating recommendations. +- An AWS, GCP, or Azure account configured with [Cloud Cost Recommendations][4] and actively generating recommendations. - The **Cloud Cost Management - Cloud Cost Management Write** permission to create or edit an automation. -- A [Workflow Automation connection][5] to each AWS account you want an automation to act on. Datadog uses this connection to assume an IAM role with the write permissions needed for the recommended action. Datadog grants only the permissions required for the selected recommendation type. +- A connection to each account you want an automation to act on, set up from {{< ui >}}Manage Connections{{< /ui >}} on the {{< ui >}}Automations{{< /ui >}} page. Datadog uses this connection to assume a role with the write permissions needed for the recommended action, and grants only the permissions required for the selected recommendation type. To act across multiple accounts with one automation, create a [connection group][7]. - (Optional) A Slack or Microsoft Teams connection if you want approval messages routed to a channel. ## Set up an automation @@ -56,16 +73,17 @@ Cost Optimization Automation supports the following AWS recommendation types: To set up an automation on a recurring schedule for a recommendation type: 1. Navigate to [{{< ui >}}Cloud Cost{{< /ui >}} > {{< ui >}}Optimize{{< /ui >}} > {{< ui >}}Automations{{< /ui >}}][6]. +1. Select the {{< ui >}}Remediation{{< /ui >}} tab. 1. On the left side of the page, select the recommendation type. 1. Click **Create New Automation**. -1. In the {{< ui >}}AWS Connection{{< /ui >}} dropdown menu, select or create a [connection][5]. To act across multiple accounts with one automation, select or create a [connection group][7]. +1. In the {{< ui >}}Connection{{< /ui >}} dropdown menu, select a connection or connection group configured in [{{< ui >}}Manage Connections{{< /ui >}}][5]. 1. In the {{< ui >}}Define scope{{< /ui >}} section: 1. Enter tags to restrict the automation to resources matching those tags, such as `env`, `service`, and `team`. 1. Enter the maximum resources per run to cap how many resources the automation acts on during a single execution. The automation prioritizes resources by highest potential savings. 1. In the {{< ui >}}Set schedule{{< /ui >}} section, select the automation frequency and execution time. 1. (Optional) Enable the {{< ui >}}Require approval before execution{{< /ui >}} toggle to require human review before execution. If enabled, select {{< ui >}}Slack{{< /ui >}} or {{< ui >}}Microsoft Teams{{< /ui >}}, and fill out the channel notification fields. See [Safeguards](#safeguards). 1. Enter a name for the automation. -1. Click {{< ui >}}Save Policy{{< /ui >}}. +1. Click {{< ui >}}Save Automation{{< /ui >}}. ### Safeguards @@ -75,7 +93,7 @@ If {{< ui >}}Require approval before execution{{< /ui >}} is enabled in the [aut ## Manage automations -The {{< ui >}}Automations{{< /ui >}} page lists every automation in your organization, grouped by recommendation type. From this page you can: +The {{< ui >}}Remediation{{< /ui >}} tab lists every automation (labeled as a **policy** in this view) in your organization, grouped by recommendation type. Use the {{< ui >}}Provider{{< /ui >}}, {{< ui >}}Resource Type{{< /ui >}}, and {{< ui >}}Recommendation Type{{< /ui >}} filters at the top of the page to narrow the list. From this page you can: - Pause or resume an automation - Edit an automation's scope, schedule, or safeguards @@ -114,3 +132,4 @@ If you set a recommendation to {{< ui >}}Dismissed{{< /ui >}}, automations skip [5]: /actions/connections/ [6]: https://app.datadoghq.com/cost/optimize/automations [7]: /actions/connections/#connection-groups +[8]: /cloud_cost_management/recommendations/automated_notifications/ From 9f63aafbeda883b8ad67f17de82afa88d461a239 Mon Sep 17 00:00:00 2001 From: "zeina.gebran" Date: Fri, 7 Aug 2026 14:51:18 +0200 Subject: [PATCH 02/10] Update notification Define scope step to reflect the new filter bar --- .../recommendations/automated_notifications.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hugo/content/en/cloud_cost_management/recommendations/automated_notifications.md b/hugo/content/en/cloud_cost_management/recommendations/automated_notifications.md index d4d24e637f5..08a166e180f 100644 --- a/hugo/content/en/cloud_cost_management/recommendations/automated_notifications.md +++ b/hugo/content/en/cloud_cost_management/recommendations/automated_notifications.md @@ -30,7 +30,7 @@ To set up a notification rule: 1. Navigate to [{{< ui >}}Cloud Cost{{< /ui >}} > {{< ui >}}Optimize{{< /ui >}} > {{< ui >}}Automations{{< /ui >}}][4]. 1. Select the {{< ui >}}Notification{{< /ui >}} tab. -1. In the {{< ui >}}Define scope{{< /ui >}} section, enter tags to restrict the notification to resources matching those tags. Leave this blank to include all resources. +1. In the {{< ui >}}Define scope{{< /ui >}} section, use the {{< ui >}}Team{{< /ui >}}, {{< ui >}}Recommendation Type{{< /ui >}}, and {{< ui >}}Env{{< /ui >}} filters to restrict the notification to matching resources. Click {{< ui >}}+ Filter{{< /ui >}} to add more filters. Leave the filters empty to include all resources. 1. In the {{< ui >}}Set schedule{{< /ui >}} section, select the notification frequency, execution day, execution time, and timezone. 1. In the destination section, select a Slack workspace connection and channel. 1. Enter a name for the notification rule. From 5cc67fa61827af91eb3bc994b1381c912e02768a Mon Sep 17 00:00:00 2001 From: "zeina.gebran" Date: Fri, 7 Aug 2026 14:58:18 +0200 Subject: [PATCH 03/10] Address review feedback: wrap Destination in ui shortcode, renumber refs, match menu name to page title --- hugo/config/_default/menus/main.en.yaml | 2 +- .../recommendations/_index.md | 18 +++++++++--------- .../recommendations/automated_notifications.md | 2 +- 3 files changed, 11 insertions(+), 11 deletions(-) diff --git a/hugo/config/_default/menus/main.en.yaml b/hugo/config/_default/menus/main.en.yaml index 68e396a3f77..df4281ab55a 100644 --- a/hugo/config/_default/menus/main.en.yaml +++ b/hugo/config/_default/menus/main.en.yaml @@ -4222,7 +4222,7 @@ menu: parent: cloud_cost identifier: cloud_cost_recommendations weight: 7 - - name: Cost Optimization Automation + - name: Cost Optimization Automations url: cloud_cost_management/recommendations/cost_optimization_automation parent: cloud_cost_recommendations identifier: cloud_cost_optimization_automation diff --git a/hugo/content/en/cloud_cost_management/recommendations/_index.md b/hugo/content/en/cloud_cost_management/recommendations/_index.md index 73c326353de..c4c179b8661 100644 --- a/hugo/content/en/cloud_cost_management/recommendations/_index.md +++ b/hugo/content/en/cloud_cost_management/recommendations/_index.md @@ -697,7 +697,7 @@ You can see the detailed logic for each recommendation type, along with observab Recommendations support [Tag Pipelines][11], allowing you to filter, group, and analyze recommendations using your organization's standardized tags. Any tag rules configured in Tag Pipelines are automatically applied to recommendations and [are normalized][12]. -You can also query your recommendations from an AI agent with the [`cost_recommendations`][16] tool in the Datadog MCP Server. +You can also query your recommendations from an AI agent with the [`cost_recommendations`][17] tool in the Datadog MCP Server. ## Recommendation categories @@ -719,8 +719,8 @@ The following are requirements necessary to receive Cloud Cost recommendations: - [AWS integration and resource collection][3] (for AWS recommendations) - [Azure integration and resource collection][8] (for Azure recommendations) - [GCP integration and resource collection][10] (for GCP recommendations) -- [OpenAI integration][17] (for OpenAI recommendations) -- [Anthropic integration][18] (for Anthropic recommendations) +- [OpenAI integration][18] (for OpenAI recommendations) +- [Anthropic integration][19] (for Anthropic recommendations) - [Datadog Agent integration][5] (for Downsize recommendations) ## Setup @@ -800,8 +800,8 @@ You can act on recommendations to save money and optimize costs. Cloud Cost Reco - **[Bits Code][14] code fixes**: Code fixes are available for applicable S3 and DynamoDB recommendations, as well as the Downsize Kubernetes Deployment recommendation. In these situations, Bits Code creates production-ready pull requests to implement cloud resource changes and cost optimizations in Terraform or Helm charts, respectively. [Set up Bits Code][13] to use this feature. - **1-click Workflow Automation actions**: Actions are available for a limited set of recommendations, allowing users to execute suggested actions, such as clicking {{< ui >}}Delete EBS Volume{{< /ui >}}, directly within Cloud Cost Management. -- **[Cost Optimization Automation][15]**: Set up automations that act on recommendations continuously on a recurring schedule. Automations are scoped to specific accounts, regions, and tags and include safeguards such as pre-action snapshots and optional human approval through Slack or Microsoft Teams. -- **[Automated Notifications][19]**: Set up notification rules that send a recurring Slack summary of matching recommendations, without taking any action. +- **[Cost Optimization Automations][15]**: Set up automations that act on recommendations continuously on a recurring schedule. Automations are scoped to specific accounts, regions, and tags and include safeguards such as pre-action snapshots and optional human approval through Slack or Microsoft Teams. +- **[Automated Notifications][16]**: Set up notification rules that send a recurring Slack summary of matching recommendations, without taking any action. - **Datadog Case Management**: Users can go to the recommendation side panel and click {{< ui >}}Create Case{{< /ui >}} to generate a case to manage and take action on recommendations. - **Dismiss**: Use {{< ui >}}Dismiss{{< /ui >}} in the recommendation side panel to hide a recommendation for a chosen time frame and provide a reason. Dismissed recommendations move to the {{< ui >}}Dismissed{{< /ui >}} tab. @@ -828,7 +828,7 @@ You can act on recommendations to save money and optimize costs. Cloud Cost Reco [13]: /bits_ai/bits_code/setup [14]: /bits_ai/bits_code/ [15]: /cloud_cost_management/recommendations/cost_optimization_automation/ -[19]: /cloud_cost_management/recommendations/automated_notifications/ -[16]: /mcp_server/tools/#cost_recommendations -[17]: /cloud_cost_management/setup/saas_costs/?tab=openai#configure-your-saas-accounts -[18]: /cloud_cost_management/setup/saas_costs/?tab=anthropic#configure-your-saas-accounts +[16]: /cloud_cost_management/recommendations/automated_notifications/ +[17]: /mcp_server/tools/#cost_recommendations +[18]: /cloud_cost_management/setup/saas_costs/?tab=openai#configure-your-saas-accounts +[19]: /cloud_cost_management/setup/saas_costs/?tab=anthropic#configure-your-saas-accounts diff --git a/hugo/content/en/cloud_cost_management/recommendations/automated_notifications.md b/hugo/content/en/cloud_cost_management/recommendations/automated_notifications.md index 08a166e180f..1dceb5c72c8 100644 --- a/hugo/content/en/cloud_cost_management/recommendations/automated_notifications.md +++ b/hugo/content/en/cloud_cost_management/recommendations/automated_notifications.md @@ -32,7 +32,7 @@ To set up a notification rule: 1. Select the {{< ui >}}Notification{{< /ui >}} tab. 1. In the {{< ui >}}Define scope{{< /ui >}} section, use the {{< ui >}}Team{{< /ui >}}, {{< ui >}}Recommendation Type{{< /ui >}}, and {{< ui >}}Env{{< /ui >}} filters to restrict the notification to matching resources. Click {{< ui >}}+ Filter{{< /ui >}} to add more filters. Leave the filters empty to include all resources. 1. In the {{< ui >}}Set schedule{{< /ui >}} section, select the notification frequency, execution day, execution time, and timezone. -1. In the destination section, select a Slack workspace connection and channel. +1. In the {{< ui >}}Destination{{< /ui >}} section, select a Slack workspace connection and channel. 1. Enter a name for the notification rule. 1. Use the {{< ui >}}Notification enabled{{< /ui >}} toggle to control whether the rule is active. 1. Click **Save**. From 5cb348471658c5f5677c2ea89d40e5ce5069c14b Mon Sep 17 00:00:00 2001 From: "zeina.gebran" Date: Fri, 7 Aug 2026 16:07:38 +0200 Subject: [PATCH 04/10] Fix preview_links.py paths broken by the hugo/ repo reorg Points the mako template load at hugo/local/bin/py/, and updates the content/en/ path matching to also accept the hugo/ prefix so preview links resolve for files under the post-reorg layout. --- hugo/local/bin/py/preview_links.py | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/hugo/local/bin/py/preview_links.py b/hugo/local/bin/py/preview_links.py index 03ca573f780..1c720ee1777 100644 --- a/hugo/local/bin/py/preview_links.py +++ b/hugo/local/bin/py/preview_links.py @@ -12,10 +12,10 @@ args=parser.parse_args() -comment_template = Template(filename='local/bin/py/preview-links-template.mako') +comment_template = Template(filename='hugo/local/bin/py/preview-links-template.mako') -pattern1 = re.compile('content/en/(.*?).md') -pattern2 = re.compile('content/en/glossary/terms/(.*?).md') +pattern1 = re.compile('(hugo/)?content/en/(.*?).md') +pattern2 = re.compile('(hugo/)?content/en/glossary/terms/(.*?).md') # Grab YAML frontmatter from markdown file def grab_glossary_title(filename): @@ -29,9 +29,9 @@ def compile_filename(filename): if pattern2.match(filename): return grab_glossary_title(filename) elif pattern1.match(filename): + filename = filename.split('content/en/', 1)[-1] filename = filename.replace( - 'content/en/', '' - ).replace('_index', '' + '_index', '' ).replace('.mdoc', '' ).replace('.md', '') return filename From 206454a1442d783579f064478fe97d650e17c2b4 Mon Sep 17 00:00:00 2001 From: "zeina.gebran" Date: Fri, 7 Aug 2026 16:25:04 +0200 Subject: [PATCH 05/10] Rename Automated Notifications page title to Notifications --- hugo/config/_default/menus/main.en.yaml | 2 +- .../en/cloud_cost_management/recommendations/_index.md | 2 +- .../recommendations/automated_notifications.md | 2 +- .../recommendations/cost_optimization_automation.md | 4 ++-- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/hugo/config/_default/menus/main.en.yaml b/hugo/config/_default/menus/main.en.yaml index df4281ab55a..2c38be07b05 100644 --- a/hugo/config/_default/menus/main.en.yaml +++ b/hugo/config/_default/menus/main.en.yaml @@ -4227,7 +4227,7 @@ menu: parent: cloud_cost_recommendations identifier: cloud_cost_optimization_automation weight: 700 - - name: Automated Notifications + - name: Notifications url: cloud_cost_management/recommendations/automated_notifications parent: cloud_cost_recommendations identifier: cloud_cost_automated_notifications diff --git a/hugo/content/en/cloud_cost_management/recommendations/_index.md b/hugo/content/en/cloud_cost_management/recommendations/_index.md index c4c179b8661..45d4336af90 100644 --- a/hugo/content/en/cloud_cost_management/recommendations/_index.md +++ b/hugo/content/en/cloud_cost_management/recommendations/_index.md @@ -801,7 +801,7 @@ You can act on recommendations to save money and optimize costs. Cloud Cost Reco - **[Bits Code][14] code fixes**: Code fixes are available for applicable S3 and DynamoDB recommendations, as well as the Downsize Kubernetes Deployment recommendation. In these situations, Bits Code creates production-ready pull requests to implement cloud resource changes and cost optimizations in Terraform or Helm charts, respectively. [Set up Bits Code][13] to use this feature. - **1-click Workflow Automation actions**: Actions are available for a limited set of recommendations, allowing users to execute suggested actions, such as clicking {{< ui >}}Delete EBS Volume{{< /ui >}}, directly within Cloud Cost Management. - **[Cost Optimization Automations][15]**: Set up automations that act on recommendations continuously on a recurring schedule. Automations are scoped to specific accounts, regions, and tags and include safeguards such as pre-action snapshots and optional human approval through Slack or Microsoft Teams. -- **[Automated Notifications][16]**: Set up notification rules that send a recurring Slack summary of matching recommendations, without taking any action. +- **[Notifications][16]**: Set up notification rules that send a recurring Slack summary of matching recommendations, without taking any action. - **Datadog Case Management**: Users can go to the recommendation side panel and click {{< ui >}}Create Case{{< /ui >}} to generate a case to manage and take action on recommendations. - **Dismiss**: Use {{< ui >}}Dismiss{{< /ui >}} in the recommendation side panel to hide a recommendation for a chosen time frame and provide a reason. Dismissed recommendations move to the {{< ui >}}Dismissed{{< /ui >}} tab. diff --git a/hugo/content/en/cloud_cost_management/recommendations/automated_notifications.md b/hugo/content/en/cloud_cost_management/recommendations/automated_notifications.md index 1dceb5c72c8..c6753c92628 100644 --- a/hugo/content/en/cloud_cost_management/recommendations/automated_notifications.md +++ b/hugo/content/en/cloud_cost_management/recommendations/automated_notifications.md @@ -1,5 +1,5 @@ --- -title: Automated Notifications +title: Notifications description: Set up notification rules that send a recurring Slack summary of Cloud Cost Recommendations matching a scope you define. further_reading: - link: "/cloud_cost_management/" diff --git a/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md b/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md index 863de68b38c..08913c3a8b5 100644 --- a/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md +++ b/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md @@ -10,7 +10,7 @@ further_reading: text: "Cloud Cost Recommendations" - link: "/cloud_cost_management/recommendations/automated_notifications/" tag: "Documentation" - text: "Automated Notifications" + text: "Notifications" - link: "/actions/workflows/" tag: "Documentation" text: "Workflow Automation" @@ -32,7 +32,7 @@ Recommendations acted on by an automation move to {{< ui >}}Completed{{< /ui >}} Remediation automations are different from the 1-click Workflow Automation actions described in [Recommendation action-taking][2]. 1-click actions execute a single change on demand from the recommendation side panel. Automations execute on a recurring schedule and act on every matching resource in scope. -Remediation automations are also different from [Automated Notifications][8], which send a recurring Slack summary of matching recommendations but don't take any action. +Remediation automations are also different from [Notifications][8], which send a recurring Slack summary of matching recommendations but don't take any action. **Note**: Remediation automations use Datadog Workflows and incur additional costs. For detailed pricing information, see the [Workflow Automation pricing page][3]. From 47a65f4cd2730c2999647c76824c0b6dda952bf9 Mon Sep 17 00:00:00 2001 From: "zeina.gebran" Date: Fri, 7 Aug 2026 16:27:05 +0200 Subject: [PATCH 06/10] Rename notifications page URL to match new title Renames automated_notifications.md to notifications.md, since the page hasn't shipped yet and there's no live URL to preserve. --- hugo/config/_default/menus/main.en.yaml | 4 ++-- .../en/cloud_cost_management/recommendations/_index.md | 2 +- .../recommendations/cost_optimization_automation.md | 4 ++-- .../{automated_notifications.md => notifications.md} | 0 4 files changed, 5 insertions(+), 5 deletions(-) rename hugo/content/en/cloud_cost_management/recommendations/{automated_notifications.md => notifications.md} (100%) diff --git a/hugo/config/_default/menus/main.en.yaml b/hugo/config/_default/menus/main.en.yaml index 2c38be07b05..051fb3ebc3c 100644 --- a/hugo/config/_default/menus/main.en.yaml +++ b/hugo/config/_default/menus/main.en.yaml @@ -4228,9 +4228,9 @@ menu: identifier: cloud_cost_optimization_automation weight: 700 - name: Notifications - url: cloud_cost_management/recommendations/automated_notifications + url: cloud_cost_management/recommendations/notifications parent: cloud_cost_recommendations - identifier: cloud_cost_automated_notifications + identifier: cloud_cost_notifications weight: 701 - name: Custom Recommendations url: cloud_cost_management/recommendations/custom_recommendations diff --git a/hugo/content/en/cloud_cost_management/recommendations/_index.md b/hugo/content/en/cloud_cost_management/recommendations/_index.md index 45d4336af90..3677431492b 100644 --- a/hugo/content/en/cloud_cost_management/recommendations/_index.md +++ b/hugo/content/en/cloud_cost_management/recommendations/_index.md @@ -828,7 +828,7 @@ You can act on recommendations to save money and optimize costs. Cloud Cost Reco [13]: /bits_ai/bits_code/setup [14]: /bits_ai/bits_code/ [15]: /cloud_cost_management/recommendations/cost_optimization_automation/ -[16]: /cloud_cost_management/recommendations/automated_notifications/ +[16]: /cloud_cost_management/recommendations/notifications/ [17]: /mcp_server/tools/#cost_recommendations [18]: /cloud_cost_management/setup/saas_costs/?tab=openai#configure-your-saas-accounts [19]: /cloud_cost_management/setup/saas_costs/?tab=anthropic#configure-your-saas-accounts diff --git a/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md b/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md index 08913c3a8b5..b03d1889c98 100644 --- a/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md +++ b/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md @@ -8,7 +8,7 @@ further_reading: - link: "/cloud_cost_management/recommendations/" tag: "Documentation" text: "Cloud Cost Recommendations" -- link: "/cloud_cost_management/recommendations/automated_notifications/" +- link: "/cloud_cost_management/recommendations/notifications/" tag: "Documentation" text: "Notifications" - link: "/actions/workflows/" @@ -132,4 +132,4 @@ If you set a recommendation to {{< ui >}}Dismissed{{< /ui >}}, automations skip [5]: /actions/connections/ [6]: https://app.datadoghq.com/cost/optimize/automations [7]: /actions/connections/#connection-groups -[8]: /cloud_cost_management/recommendations/automated_notifications/ +[8]: /cloud_cost_management/recommendations/notifications/ diff --git a/hugo/content/en/cloud_cost_management/recommendations/automated_notifications.md b/hugo/content/en/cloud_cost_management/recommendations/notifications.md similarity index 100% rename from hugo/content/en/cloud_cost_management/recommendations/automated_notifications.md rename to hugo/content/en/cloud_cost_management/recommendations/notifications.md From ad05decd3ab5321f79b8d0a3455abf1306ab765d Mon Sep 17 00:00:00 2001 From: "zeina.gebran" Date: Tue, 11 Aug 2026 10:22:11 +0200 Subject: [PATCH 07/10] Address review feedback on safeguards table, UI shortcodes, and notification prerequisites Normalize the safeguards table to consistent phrasing, fix the EBS snapshot optional/unconditional contradiction, restore the S3 Intelligent-Tiering reversibility fact alongside the preserved-rules fact, remove a duplicated safeguards sentence, switch remaining bold UI references to the ui shortcode, and add the required permission to the Notifications prerequisites. --- .../cost_optimization_automation.md | 20 +++++++++---------- .../recommendations/notifications.md | 5 +++-- 2 files changed, 13 insertions(+), 12 deletions(-) diff --git a/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md b/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md index b03d1889c98..e84e07a591f 100644 --- a/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md +++ b/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md @@ -42,8 +42,8 @@ The {{< ui >}}Remediation{{< /ui >}} tab supports the following recommendation t | Provider | Recommendation type | Built-in safeguards | |----------|---------------------|---------------------| -| AWS | Delete unattached EBS volume | Optional: takes an EBS snapshot before each volume is deleted. | -| AWS | Migrate EBS volume from gp2 to gp3 | Reversible, in-place migration with no data loss. | +| AWS | Delete unattached EBS volume | (Optional) Takes an EBS snapshot before each volume is deleted. | +| AWS | Migrate EBS volume from gp2 to gp3 | Reversible. The migration causes no data loss. | | AWS | Delete unused EBS snapshots | Snapshots referenced by an AMI are skipped. | | AWS | Delete extra on-demand backups (DynamoDB) | The two most recent backups are preserved on every run. | | AWS | Migrate DynamoDB table to Infrequent Access table class | Reversible. The table class can be changed back at any time. | @@ -51,15 +51,15 @@ The {{< ui >}}Remediation{{< /ui >}} tab supports the following recommendation t | AWS | Set CloudWatch logs retention policy | Reversible. The retention period can be adjusted or removed at any time. | | AWS | Delete unused RDS instance | A final RDS snapshot is taken before each instance is deleted. | | AWS | Delete unused NAT gateway | None. Deletion is irreversible. | -| AWS | Transition S3 Standard objects to Amazon S3 Intelligent-Tiering | Existing lifecycle rules are preserved rather than overwritten. | -| AWS | Delete unused EC2 instance | Optional: creates an AMI before each instance is deleted. | +| AWS | Transition S3 Standard objects to Amazon S3 Intelligent-Tiering | Reversible. Existing lifecycle rules are preserved, and the added rule can be removed at any time. | +| AWS | Delete unused EC2 instance | (Optional) Creates an AMI before each instance is deleted. | | AWS | Delete unused Redshift cluster | A final snapshot is taken before each cluster is deleted. | -| GCP | Delete unattached Compute Engine disk | Optional: takes a snapshot before each disk is deleted. | +| GCP | Delete unattached Compute Engine disk | (Optional) Takes a snapshot before each disk is deleted. | | GCP | Enable Autoclass on a Cloud Storage bucket | Reversible. Autoclass can be disabled at any time. | -| Azure | Delete unattached managed disk | Optional: takes a snapshot before each disk is deleted. | +| Azure | Delete unattached managed disk | (Optional) Takes a snapshot before each disk is deleted. | | Azure | Delete unused SQL database | None. Deletion is irreversible. | -Safeguards marked "Optional" are enabled by default and can be turned off in the automation form. All other listed safeguards are always applied and can't be disabled. +Safeguards marked (Optional) are enabled by default and can be turned off in the automation form. All other listed safeguards are always applied and can't be disabled. ## Prerequisites @@ -75,7 +75,7 @@ To set up an automation on a recurring schedule for a recommendation type: 1. Navigate to [{{< ui >}}Cloud Cost{{< /ui >}} > {{< ui >}}Optimize{{< /ui >}} > {{< ui >}}Automations{{< /ui >}}][6]. 1. Select the {{< ui >}}Remediation{{< /ui >}} tab. 1. On the left side of the page, select the recommendation type. -1. Click **Create New Automation**. +1. Click {{< ui >}}Create New Automation{{< /ui >}}. 1. In the {{< ui >}}Connection{{< /ui >}} dropdown menu, select a connection or connection group configured in [{{< ui >}}Manage Connections{{< /ui >}}][5]. 1. In the {{< ui >}}Define scope{{< /ui >}} section: 1. Enter tags to restrict the automation to resources matching those tags, such as `env`, `service`, and `team`. @@ -87,13 +87,13 @@ To set up an automation on a recurring schedule for a recommendation type: ### Safeguards -Each recommendation type has built-in safeguards. For example, the **Delete Unattached EBS Volume** automation takes an EBS snapshot before deleting each volume. Review the safeguards listed in the automation form and toggle the ones that are optional for your environment. +Each recommendation type has built-in safeguards. For example, the **Delete Unattached EBS Volume** automation can take an EBS snapshot before deleting each volume. See [Supported recommendation types](#supported-recommendation-types) for the full list of safeguards by recommendation type. If {{< ui >}}Require approval before execution{{< /ui >}} is enabled in the [automation setup](#set-up-an-automation), Datadog posts in the designated channel a summary of the resources targeted on each run. The automation only runs after a user approves the request in the channel. ## Manage automations -The {{< ui >}}Remediation{{< /ui >}} tab lists every automation (labeled as a **policy** in this view) in your organization, grouped by recommendation type. Use the {{< ui >}}Provider{{< /ui >}}, {{< ui >}}Resource Type{{< /ui >}}, and {{< ui >}}Recommendation Type{{< /ui >}} filters at the top of the page to narrow the list. From this page you can: +The {{< ui >}}Remediation{{< /ui >}} tab lists every automation in your organization, grouped by recommendation type. Automations are labeled **policies** in this view. Use the {{< ui >}}Provider{{< /ui >}}, {{< ui >}}Resource Type{{< /ui >}}, and {{< ui >}}Recommendation Type{{< /ui >}} filters at the top of the page to narrow the list. From this page you can: - Pause or resume an automation - Edit an automation's scope, schedule, or safeguards diff --git a/hugo/content/en/cloud_cost_management/recommendations/notifications.md b/hugo/content/en/cloud_cost_management/recommendations/notifications.md index c6753c92628..011a0cae630 100644 --- a/hugo/content/en/cloud_cost_management/recommendations/notifications.md +++ b/hugo/content/en/cloud_cost_management/recommendations/notifications.md @@ -23,6 +23,7 @@ Notification rules are different from [Cost Optimization Automations][2], which ## Prerequisites - A Slack connection. See [Slack integration][3]. +- The **Cloud Cost Management - Cloud Cost Management Write** permission to create or edit a notification rule. ## Set up a notification rule @@ -34,8 +35,8 @@ To set up a notification rule: 1. In the {{< ui >}}Set schedule{{< /ui >}} section, select the notification frequency, execution day, execution time, and timezone. 1. In the {{< ui >}}Destination{{< /ui >}} section, select a Slack workspace connection and channel. 1. Enter a name for the notification rule. -1. Use the {{< ui >}}Notification enabled{{< /ui >}} toggle to control whether the rule is active. -1. Click **Save**. +1. (Optional) Turn off the {{< ui >}}Notification enabled{{< /ui >}} toggle to create the rule without activating it. +1. Click {{< ui >}}Save{{< /ui >}}. ## Manage notification rules From a049f5c0fcd8c4b8451e42f77952bd34f6e3adda Mon Sep 17 00:00:00 2001 From: "zeina.gebran" Date: Tue, 11 Aug 2026 10:38:45 +0200 Subject: [PATCH 08/10] Bridge Remediation tab terminology to Cost Optimization Automations Address Olivia's review comment: open the Overview with the page's own term and mention the UI tab once, then use plain "Automations" for the rest of the comparisons for consistency. --- .../recommendations/cost_optimization_automation.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md b/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md index e84e07a591f..6118108cf54 100644 --- a/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md +++ b/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md @@ -19,7 +19,7 @@ further_reading: ## Overview -The {{< ui >}}Remediation{{< /ui >}} tab lets you continuously act on [Cloud Cost Recommendations][1] without manual cleanup. You define an **automation**, scope it to the accounts, regions, and resources you want, and Datadog executes the recommended action on a recurring schedule. Each run can require human approval in Slack or Microsoft Teams before Datadog makes any changes, so your team stays in control of every change. +Cost Optimization Automations let you continuously act on [Cloud Cost Recommendations][1] without manual cleanup. In the {{< ui >}}Automations{{< /ui >}} page, they live on the {{< ui >}}Remediation{{< /ui >}} tab. You define an **automation**, scope it to the accounts, regions, and resources you want, and Datadog executes the recommended action on a recurring schedule. Each run can require human approval in Slack or Microsoft Teams before Datadog makes any changes, so your team stays in control of every change. Each automation targets a single recommendation type and includes the following: @@ -30,11 +30,11 @@ Each automation targets a single recommendation type and includes the following: Recommendations acted on by an automation move to {{< ui >}}Completed{{< /ui >}} automatically and contribute to realized savings on the [Cloud Cost Recommendations][1] page. -Remediation automations are different from the 1-click Workflow Automation actions described in [Recommendation action-taking][2]. 1-click actions execute a single change on demand from the recommendation side panel. Automations execute on a recurring schedule and act on every matching resource in scope. +Automations are different from the 1-click Workflow Automation actions described in [Recommendation action-taking][2]. 1-click actions execute a single change on demand from the recommendation side panel. Automations execute on a recurring schedule and act on every matching resource in scope. -Remediation automations are also different from [Notifications][8], which send a recurring Slack summary of matching recommendations but don't take any action. +Automations are also different from [Notifications][8], which send a recurring Slack summary of matching recommendations but don't take any action. -**Note**: Remediation automations use Datadog Workflows and incur additional costs. For detailed pricing information, see the [Workflow Automation pricing page][3]. +**Note**: Automations use Datadog Workflows and incur additional costs. For detailed pricing information, see the [Workflow Automation pricing page][3]. ## Supported recommendation types From 1f94c7189bb04acb24e534a3dd9e06a9059bfe35 Mon Sep 17 00:00:00 2001 From: "zeina.gebran" Date: Tue, 11 Aug 2026 15:17:56 +0200 Subject: [PATCH 09/10] Fix automation permission prerequisite to match backend RBAC gate The Cost Optimization Automation CRUD is backed by real Workflow Automation objects and is gated by the Workflows Write permission, not Cloud Cost Management Write. --- .../recommendations/cost_optimization_automation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md b/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md index 6118108cf54..f396dee74c9 100644 --- a/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md +++ b/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md @@ -64,7 +64,7 @@ Safeguards marked (Optional) are enabled by default and can be turned off in the ## Prerequisites - An AWS, GCP, or Azure account configured with [Cloud Cost Recommendations][4] and actively generating recommendations. -- The **Cloud Cost Management - Cloud Cost Management Write** permission to create or edit an automation. +- The **App Builder & Workflow Automation - Workflows Write** permission to create or edit an automation. - A connection to each account you want an automation to act on, set up from {{< ui >}}Manage Connections{{< /ui >}} on the {{< ui >}}Automations{{< /ui >}} page. Datadog uses this connection to assume a role with the write permissions needed for the recommended action, and grants only the permissions required for the selected recommendation type. To act across multiple accounts with one automation, create a [connection group][7]. - (Optional) A Slack or Microsoft Teams connection if you want approval messages routed to a channel. From d22ccbc50e4663f2ef8954d88b7dfe5c25e84198 Mon Sep 17 00:00:00 2001 From: "zeina.gebran" Date: Tue, 11 Aug 2026 15:50:08 +0200 Subject: [PATCH 10/10] Clarify automation prerequisites need both CCM Write and Workflows Write Access to the Automations page requires Cloud Cost Management Write at the route level; creating or editing an automation additionally requires Workflows Write at the component level. These are two separate, both-required permissions, not either/or. --- .../recommendations/cost_optimization_automation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md b/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md index f396dee74c9..4dce5a964e4 100644 --- a/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md +++ b/hugo/content/en/cloud_cost_management/recommendations/cost_optimization_automation.md @@ -64,7 +64,7 @@ Safeguards marked (Optional) are enabled by default and can be turned off in the ## Prerequisites - An AWS, GCP, or Azure account configured with [Cloud Cost Recommendations][4] and actively generating recommendations. -- The **App Builder & Workflow Automation - Workflows Write** permission to create or edit an automation. +- The **Cloud Cost Management - Cloud Cost Management Write** permission to access the {{< ui >}}Automations{{< /ui >}} page, and the **App Builder & Workflow Automation - Workflows Write** permission to create or edit an automation. - A connection to each account you want an automation to act on, set up from {{< ui >}}Manage Connections{{< /ui >}} on the {{< ui >}}Automations{{< /ui >}} page. Datadog uses this connection to assume a role with the write permissions needed for the recommended action, and grants only the permissions required for the selected recommendation type. To act across multiple accounts with one automation, create a [connection group][7]. - (Optional) A Slack or Microsoft Teams connection if you want approval messages routed to a channel.