AWS Security ChangesHomeSearch

AWS amazonq: Datadog plugin doc replaced with pointer to AWS assistant guide

Service: amazonq · 2026-11-06 · Documentation low

File: amazonq/latest/qdeveloper-ug/datadog-plugin.md

Summary

The entire Datadog plugin page content (prerequisites, Secrets Manager secret format, IAM service role and trust policy examples, plugin configuration steps, and user permission guidance) was removed and replaced with a single sentence plus a link stating the Datadog plugin is now part of the AWS assistant and pointing to the new AWS assistant User Guide.

Security assessment

This is a documentation relocation/deprecation: the page is stubbed out and redirected to a new location. No vulnerability, CVE, or incident is referenced, and no new security guidance is added (security content such as the Secrets Manager secret JSON format and IAM service role/trust policies was removed, not introduced).

Evidence

For current documentation, see [Configuring the AWS assistant Datadog plugin](https://docs.aws.amazon.com/assistant/latest/userguide/datadog-plugin.html) in the _AWS assistant User Guide_.

Diff

diff --git a/amazonq/latest/qdeveloper-ug/datadog-plugin.md b/amazonq/latest/qdeveloper-ug/datadog-plugin.md
index 4ff402b..8202b53 100644
--- a//amazonq/latest/qdeveloper-ug/datadog-plugin.md
+++ b//amazonq/latest/qdeveloper-ug/datadog-plugin.md
@@ -7,2 +6,0 @@
-PrerequisitesSecrets and service rolesConfigure the Datadog pluginConfigure user permissionsChat with the Datadog plugin
-
@@ -11,252 +9 @@ PrerequisitesSecrets and service rolesConfigure the Datadog pluginConfigure user
-Datadog is a monitoring and security platform that provides infrastructure, application, and network monitoring and analytics. If you use Datadog to monitor your AWS applications, you can use the Datadog plugin in Amazon Q Developer chat to access monitoring information without leaving the AWS Management Console.
-
-You can use the Datadog plugin to learn about Datadog, understand how it works with AWS services, and ask about your Datadog cases and monitors. After you receive a response, you can ask follow up questions, including how to address an issue or for details about Datadog resources.
-
-To configure the plugin, you provide authentication credentials from your Datadog account to enable a connection between Amazon Q and Datadog. After you configure the plugin, you can access Datadog metrics by adding ``@datadog`` to the beginning of your question in Amazon Q chat. 
-
-###### Warning
-
-Datadog user permissions are not detected by the Datadog plugin in Amazon Q. When an administrator configures the Datadog plugin in an AWS account, users with plugin permissions in that account have access to any resources in the Datadog account retrievable by the plugin. 
-
-You can configure IAM policies to restrict which plugins users have access to. For more information, see Configure user permissions.
-
-## Prerequisites
-
-### Add permissions
-
-To configure plugins, the following administrator level permissions are required: 
-
-  * Permissions to access the Amazon Q Developer console. For an example IAM policy that grants needed permissions, see [Allow administrators to use the Amazon Q Developer console](./id-based-policy-examples-admins.html#q-admin-setup-admin-users).
-
-  * Permissions to configure plugins. For an example IAM policy that grants the needed permissions, see [Allow administrators to configure plugins](./id-based-policy-examples-admins.html#id-based-policy-examples-admin-plugins).
-
-
-
-
-### Acquire credentials
-
-Before you begin, note the following information from your Datadog account. These authentication credentials will be stored in an AWS Secrets Manager secret when you configure the plugin. 
-
-  * **Site parameter** – The Datadog site parameter you use. For example, `us3.datadoghq.com`. For more information, see [Getting Started with Datadog Sites](https://docs.datadoghq.com/getting_started/site/) in the Datadog documentation. 
-
-  * **API key and application key** – Access keys that allow Amazon Q to call the Datadog API to access events and metrics. You can find these under **Organization Settings** in your Datadog account. For more information, see [API and Application Keys](https://docs.datadoghq.com/account_management/api-app-keys/) in the Datadog documentation. 
-
-
-
-
-## Secrets and service roles
-
-### AWS Secrets Manager secret
-
-When you configure the plugin, Amazon Q creates a new AWS Secrets Manager secret for you to store Datadog authentication credentials. Alternatively, you can use an existing secret that you create yourself.
-
-If you create a secret yourself, make sure it includes the following credentials and uses the following JSON format:
-    
-    
-    { 
-       "ApiKey": "<your-api-key>", 
-       "AppKey": "<your-applicaiton-key>" 
-    }
-
-For more information about creating secrets, see [Create a secret](https://docs.aws.amazon.com/secretsmanager/latest/userguide/create_secret.html) in the _AWS Secrets Manager User Guide_.
-
-### Service roles
-
-To configure the Datadog plugin in Amazon Q Developer, you need to create a service role that gives Amazon Q permission to access your Secrets Manager secret. Amazon Q assumes this role to access the secret where your Datadog credentials are stored.
-
-When you configure the plugin in the AWS console, you have the option to create a new secret or use an existing one. If you create a new secret, the associated service role is created for you. If you use an existing secret and an existing service role, make sure your service role contains the following permissions, and has the following trust policy attached. The service role required depends on your secret encryption method.
-
-If your secret is encrypted with an AWS managed KMS key, the following IAM service role is required:
-
-JSON
-    
-
-****
-    
-    
-    
-    {
-        "Version":"2012-10-17",
-        "Statement": [
-            {
-                "Effect": "Allow",
-                "Action": [
-                    "secretsmanager:GetSecretValue"
-                ],
-                "Resource": [
-                    "arn:aws:secretsmanager:us-east-1:111122223333:secret:secret-id"
-                ]
-            }
-        ]
-    }
-    
-
-Show moreShow less
-
-If your secret is encrypted with a customer managed AWS KMS key, the following IAM service role is required:
-
-JSON
-    
-
-****
-    
-    
-    
-    {
-        "Version":"2012-10-17",
-        "Statement": [
-            {
-                "Effect": "Allow",
-                "Action": [
-                    "secretsmanager:GetSecretValue"
-                ],
-                "Resource": "arn:aws:secretsmanager:us-east-1:111122223333:secret:secret-id"
-            },
-            {
-                "Effect": "Allow",
-                "Action": [
-                    "kms:Decrypt"
-                ],
-                "Resource": "arn:aws:kms:us-east-1:111122223333:key/key-id",
-                "Condition": {
-                    "StringEquals": {
-                        "kms:ViaService": "secretsmanager.us-east-1.amazonaws.com"
-                    }
-                }
-            }
-        ]
-    }
-    
-
-Show moreShow less
-
-To allow Amazon Q to assume the service role, the service role needs the following trust policy: 
-
-###### Note
-
-The `codewhisperer` prefix is a legacy name from a service that merged with Amazon Q Developer. For more information, see [Amazon Q Developer rename - Summary of changes](./service-rename.html). 
-
-JSON
-    
-
-****
-    
-    
-    
-    {
-      "Version":"2012-10-17",
-      "Statement": [
-        {
-          "Effect": "Allow",
-          "Principal": {
-            "Service": "q.amazonaws.com"
-          },
-          "Action": ["sts:AssumeRole", "sts:SetContext"],
-          "Condition": {
-            "StringEquals": {
-              "aws:SourceAccount": "111122223333",
-              "aws:SourceArn": "arn:aws:codewhisperer:us-east-1:111122223333:profile/profile-id"
-            }
-          }
-        }
-      ]
-    }
-    
-
-Show moreShow less
-
-For more information about service roles, see [Create a role to delegate permissions to an AWS service](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-service.html) in the _AWS Identity and Access Management User Guide_.
-
-## Configure the Datadog plugin
-
-You configure plugins in the Amazon Q Developer console. Amazon Q uses credentials stored in AWS Secrets Manager to enable interactions with Datadog. 
-
-To configure the Datadog plugin, complete the following procedure: 
-
-  1. Open the Amazon Q Developer console at [https://console.aws.amazon.com/amazonq/developer/home](https://console.aws.amazon.com/amazonq/developer/home)
-
-  2. On the Amazon Q Developer console home page, choose **Settings**. 
-
-  3. In the navigation bar, choose **Plugins**.
-
-  4. On the plugins page, choose the plus sign on the **Datadog** panel. The plugin configuration page opens. 
-
-  5. For **Site URL** , enter the URL of the Datadog site you use. 
-
-  6. For **Configure AWS Secrets Manager** , choose either **Create a new secret** or **Use an existing secret**. The Secrets Manager secret is where your Datadog authentication credentials will be stored.
-
-If you create a new secret, enter the following information:
-
-    1. For **Datadog API key** , enter the API key for your Datadog organization.
-
-    2. For **Datadog application key** , enter the application key for your Datadog account. 
-
-    3. A service role will be created that Amazon Q will use to access the secret where your Datadog credentials are stored. Do not edit the service role that is created for you. 
-
-If you use an existing secret, choose a secret from the **AWS Secrets Manager secret** dropdown menu. The secret should include the Datadog authentication credentials specified in the previous step.
-
-For more information about the required credentials, see Acquire credentials. 
-
-  7. For **Configure AWS IAM service role** , choose either **Create new service role** or **Use existing service role**. 
-
-###### Note