Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

AWS Logo
Menu
Setting Up Amazon Q Developer Operational Investigations (Preview)

Setting Up Amazon Q Developer Operational Investigations (Preview)

Learn how to configure Investigation groups required for Amazon Q Developer's operational investigations feature. This guide walks you through the setup process across AWS regions, enabling you to use AI-powered system telemetry analysis for your operational needs.

generativeaicloudoperationsawsamazon-qcloud-operations
Raj
Amazon Employee
Published Mar 6, 2025
Comments

Amazon Q Developer operational investigations (Preview)

Note: The Amazon Q Developer operational investigations feature is in preview release and is subject to change. It is currently available only in the US East (N. Virginia) and US West (Oregon) Regions as of Mar 6 2025

Introduction:

The Amazon Q Developer operational investigations feature is a generative AI-powered assistant that can help you respond to incidents in your system. It uses generative AI to scan your system's telemetry and quickly surface suggestions that might be related to your issue.
Before you start using Amazon Q developer to assist you with operational investigations, you have to configure Investigation group for the account in each region where you plan to use Amazon Q Developer operational investigations. In this post we will go over step by step procedure to configure Investigation group with screenshots.

AWS services where investigations are supported

https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Investigations-Services.html

Configuration steps:

You will be presented with below screen when you land at overview page of AI Operations under CloudWatch,
First go to CloudWatch -> AI Operations overview
Image not found
operations overview
then, click on configure for this account.
Image not found
configure
Update retention period,
Image not found
retention
Your data is encrypted by default with a key that AWS owns and manages for you. To choose a different key, customize your encryption settings in the same page,
then,
add tags as required,
configure CloudTrail,
Image not found
trail
if you don't see CloudTrail in drop down, associate CloudTrail with cloudwatch logs in CloudTrail console,
Image not found
cloudwatch-trail
  1. (Optional) Set up X-Ray (Setting up to use X-Ray helps Amazon Q Developer better navigate and understand your application structure.)
  2. (Optional) Application Signals for health assessment (Setting up to use Application Signals helps Amazon Q Developer better understand the health of your applications, services, and dependencies.)
You can then configure
Third-party integrations as applicable,
Image not found
complete
and then click on complete.
Image not found
completion
You should see the completion of configuration.

Conclusion:

In this guide, we covered how to configure Investigation groups for Amazon Q Developer operational investigations. Following these steps will enable AI-powered system analysis in your AWS environment.

References:

Details as outlined in: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Investigations-GetStarted.html
(Recommended) Best practices to enhance investigations: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Investigations-RecommendedServices.html
If this is helpful, pls comment so I can share more step-by-step procedures for other optional steps as outlined above and for other configurations under this topic.
Image generated by Amazon Nova
 

Any opinions in this post are those of the individual author and may not reflect the opinions of AWS.

Comments

Comments

Log in to comment