AWS AmazonCloudWatch documentation change
Summary
Removed references to Amazon Q Developer operational investigations preview features, third-party ticketing systems, and AWS IAM Identity Center integration. Updated terminology to 'CloudWatch investigations' and streamlined chat integration documentation.
Security assessment
Changes primarily involve rebranding (Amazon Q Developer to CloudWatch investigations) and removing deprecated features (ticketing system/IAM Identity Center integration). No concrete evidence of security vulnerability fixes or explicit new security guidance. IAM permission references remain but are not new security documentation.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/Investigations-Integrations.md b/AmazonCloudWatch/latest/monitoring/Investigations-Integrations.md index 77e064e55..2503e6995 100644 --- a//AmazonCloudWatch/latest/monitoring/Investigations-Integrations.md +++ b//AmazonCloudWatch/latest/monitoring/Investigations-Integrations.md @@ -5 +5 @@ -Integration with AWS Systems Manager AutomationThird-party ticketing systemsIntegration with third-party chat systemsAWS IAM Identity Center +Integration with AWS Systems Manager AutomationIntegration with third-party chat systems @@ -9,31 +8,0 @@ Integration with AWS Systems Manager AutomationThird-party ticketing systemsInte -###### Note - -The Amazon Q Developer operational investigations feature is in preview release and is subject to change. It is currently available in the following Regions: - - * US East (N. Virginia) - - * US East (Ohio) - - * US West (Oregon) - - * Asia Pacific (Hong Kong) - - * Asia Pacific (Mumbai) - - * Asia Pacific (Singapore) - - * Asia Pacific (Sydney) - - * Asia Pacific (Tokyo) - - * Europe (Frankfurt) - - * Europe (Ireland) - - * Europe (Spain) - - * Europe (Stockholm) - - - - @@ -44,2 +12,0 @@ The Amazon Q Developer operational investigations feature is in preview release - * Third-party ticketing systems - @@ -48,2 +14,0 @@ The Amazon Q Developer operational investigations feature is in preview release - * AWS IAM Identity Center - @@ -55 +20 @@ The Amazon Q Developer operational investigations feature is in preview release -Amazon Q Developer operational investigations is integrated with Automation, a capability of AWS Systems Manager. You don't need to configure integration, but you might need to update AWS Identity and Access Management (IAM) permissions so you can use Automation runbooks. +CloudWatch investigations is integrated with Automation, a capability of AWS Systems Manager. You don't need to configure integration, but you might need to update AWS Identity and Access Management (IAM) permissions so you can use Automation runbooks. @@ -67,7 +32 @@ Automation provides over 400 AWS managed runbooks. For details about each runboo -For information about working with runbooks in an investigation, see [Reviewing and executing suggested runbook remediations for Amazon Q Developer operational investigations](./Investigations-Investigate.html#suggested-investigation-actions). - -## Third-party ticketing systems - -In the US East (N. Virginia) Region, you can integrate Amazon Q Developer operational investigations with a third-party ticketing system. Integrating with a ticketing tool enables Amazon Q Developer to send information about an investigation to that ticketing tool. For information about how to create this integration when you create an investigation group, see step 11b in [Set up operational investigations](./Investigations-GetStarted.html#Investigations-GetStarted-Group). - -This feature is available only in the US East (N. Virginia) Region. +For information about working with runbooks in an investigation, see [Reviewing and executing suggested runbook remediations for CloudWatch investigations](./Investigations-Investigate.html#suggested-investigation-actions). @@ -77 +36 @@ This feature is available only in the US East (N. Virginia) Region. -By integrating Amazon Q Developer operational investigations with Amazon Q Developer in chat applications, you can have updates from investigations sent to third-party chat services, including Slack, and Microsoft Teams. The integration is facilitated by Amazon Simple Notification Service. +By integrating CloudWatch investigations with CloudWatch investigations in chat applications, you can have updates from investigations sent to third-party chat services, including Slack, and Microsoft Teams. The integration is facilitated by Amazon Simple Notification Service. @@ -79 +38 @@ By integrating Amazon Q Developer operational investigations with Amazon Q Devel -To integrate with Amazon Q Developer in chat applications, you must complete three steps. We recommend completing the steps in the following order. +To integrate with CloudWatch investigations in chat applications, you must complete three steps. We recommend completing the steps in the following order. @@ -83 +42 @@ To integrate with Amazon Q Developer in chat applications, you must complete thr - * Configure in the Amazon Q Developer in chat applications console + * Configure in the CloudWatch investigations in chat applications console @@ -94 +53 @@ To integrate with Amazon Q Developer in chat applications, you must complete thr - * Configure Amazon Q Developer in chat applications + * Configure CloudWatch investigations in chat applications @@ -105 +64 @@ Create an Amazon SNS topic in US East (N. Virginia) to use for the integration. -To enable Amazon Q Developer operational investigations to send notifications, you must add an the following access policy to the Amazon SNS topic +To enable CloudWatch investigations to send notifications, you must add an the following access policy to the Amazon SNS topic @@ -123 +82 @@ To enable Amazon Q Developer operational investigations to send notifications, y -### Configure Amazon Q Developer in chat applications +### Configure CloudWatch investigations in chat applications @@ -125 +84 @@ To enable Amazon Q Developer operational investigations to send notifications, y -To configure Amazon Q Developer in chat applications for communication with a third-party chat service, follow the instructions in one of the following links: +To configure CloudWatch investigations in chat applications for communication with a third-party chat service, follow the instructions in one of the following links: @@ -134 +93 @@ To configure Amazon Q Developer in chat applications for communication with a th -Then, to support using AI assistant actions within chat channels you must provide the Amazon Q Developer in chat applications role with appropriate permissions. When you create a new IAM channel role for the channel, select the **Notifications** and **Amazon Q operations assistant permissions** policy templates. +Then, to support using AI assistant actions within chat channels you must provide the CloudWatch investigations in chat applications role with appropriate permissions. When you create a new IAM channel role for the channel, select the **Notifications** and **Amazon Q operations assistant permissions** policy templates. @@ -136 +95 @@ Then, to support using AI assistant actions within chat channels you must provid -Attach the **AIOpsOperatorAccess** managed IAM policy to the guardrail policies in Amazon Q Developer in chat applications. This grants permissions to Amazon Q Developer in chat applications to interact with Amazon Q Developer operational investigations and perform required actions on your behalf. +Attach the **AIOpsOperatorAccess** managed IAM policy to the guardrail policies in CloudWatch investigations in chat applications. This grants permissions to CloudWatch investigations in chat applications to interact with CloudWatch investigations and perform required actions on your behalf. @@ -142,3 +101 @@ In the channel configuration, you must also subscribe to the Amazon SNS topic th -You must use the CloudWatch console to configure Amazon Q Developer operational investigations to integrate with Amazon SNS. You can do this while you create the investigation group in your account, or later. - -For information about completing the step while you create the investigation group, see Step 9b at [Set up operational investigations](./Investigations-GetStarted.html#Investigations-GetStarted-Group). +You must use the CloudWatch console to configure CloudWatch investigations to integrate with Amazon SNS. You can do this while you create the investigation group in your account, or later. @@ -154,24 +111 @@ If you have already created an investigation group and want to add chat integrat - 3. Choose the **Third-party integrations** tab. - - 4. In the **Chat integration** section, do the following: - - * If you have already integrated Amazon Q Developer in chat applications with a third-party chat system, you can choose **Select SNS topic** to choose the Amazon SNS topic to use to send updates to about investigations. This Amazon SNS topic will relay those updates to the chat client. - - * If you want to integrate Amazon Q Developer in chat applications with a third-party chat system, choose **Configure new chat client**. For more information about setting up this configuration, see [Getting started with Amazon Q Developer in chat applications](https://docs.aws.amazon.com/chatbot/latest/adminguide/getting-started.html). - - - - -## AWS IAM Identity Center - -In the US East (N. Virginia) Region, you can integrate Amazon Q Developer operational investigations with AWS IAM Identity Center. Before you create an Amazon Q Developer operational investigations application in IAM Identity Center, make sure you complete the following prerequisites: - - * Enable an organization-level [**IAM Identity Center instance**](https://docs.aws.amazon.com/singlesignon/latest/userguide/get-set-up-for-idc.html) in your management account and [**connect the identity source**](https://docs.aws.amazon.com/singlesignon/latest/userguide/tutorials.html) in IAM Identity Center. Amazon Q Developer operational investigations doesn't support account-level IAM Identity Center instances. - -###### Note - -To minimize latency, we recommend that you use an IAM Identity Center instance created in the same Region as your Amazon Q Developer operational investigations application. However, you can also use an IAM Identity Center instance created in an AWS Region not yet supported by Amazon Q Developer operational investigations. For more information, see Cross-Region IAM Identity Center integration. - - * Enable the [**identity-aware session**](https://docs.aws.amazon.com/singlesignon/latest/userguide/identity-aware-sessions.html) on your IAM Identity Center instance. - - + 3. In the **Chat integration** section, do the following: @@ -178,0 +113 @@ To minimize latency, we recommend that you use an IAM Identity Center instance c + * If you have already integrated CloudWatch investigations in chat applications with a third-party chat system, you can choose **Select SNS topic** to choose the Amazon SNS topic to use to send updates to about investigations. This Amazon SNS topic will relay those updates to the chat client. @@ -180 +115 @@ To minimize latency, we recommend that you use an IAM Identity Center instance c -### Cross-Region IAM Identity Center integration + * If you want to integrate CloudWatch investigations in chat applications with a third-party chat system, choose **Configure new chat client**. For more information about setting up this configuration, see [Getting started with CloudWatch investigations in chat applications](https://docs.aws.amazon.com/chatbot/latest/adminguide/getting-started.html). @@ -182 +116,0 @@ To minimize latency, we recommend that you use an IAM Identity Center instance c -Amazon Q Developer operational investigations can integrate with IAM Identity Center in any commercial region where IAM Identity Center is available, including opt-in Regions. This integration works even if the Region isn't directly supported by Amazon Q Developer operational investigations. You have the flexibility to use an IAM Identity Center instance configured in a Rgion different from where Amazon Q Developer operational investigations is available. @@ -184 +117,0 @@ Amazon Q Developer operational investigations can integrate with IAM Identity Ce -When your IAM Identity Center instance is in a different Region than Amazon Q Developer operational investigations, you enable Amazon Q to make inter-Region calls to access information from your IAM Identity Center instance, such as user and application attributes. This capability allows Amazon Q Developer operational investigations to support IAM Identity Center-enabled applications regardless of regional differences. In this setup, your Amazon Q Developer operational investigations application will have access to user and application information from an IAM Identity Center instance deployed in another Region. @@ -186 +118,0 @@ When your IAM Identity Center instance is in a different Region than Amazon Q De -If your IAM Identity Center instance is in a different Region than your Amazon Q Developer operational investigations application, you might experience higher latency when using Amazon Q Developer operational investigations. This is caused by the increased overhead of making inter-Region calls. The increase in latency will be proportional to the distance between the two Regions.