AWS services where investigations are supported

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)

You can launch investigations from telemetry data (such as CloudWatch metrics, alarms, and logs), review generated anomaly signals, and explore hypotheses on investigations. Amazon Q Developer operational investigations work best when helping you with automated troubleshooting guidance on the AWS services listed below:

• Amazon EC2¹

• Amazon ECS on Amazon EC2²

• Amazon ECS on Fargate²

• Amazon EKS²

• Amazon DynamoDB

• Amazon S3

• Amazon EBS¹

• Lambda

• Amazon Kinesis Data Streams

• Amazon Data Firehose

• Amazon API Gateway

• Amazon SQS

• Amazon SNS

The list of services will continue to be expanded over time. Amazon Q Developer operational investigations utilizes a wide range of data sources to determine dependency relationships and plan analysis paths, including telemetry data configurations, service configurations, and observed relationships through CloudWatch Application Signals and X-Ray. Where none of the above is available, Amazon Q Developer operational investigations will attempt to infer dependency relationships through co-occurring telemetry anomalies.

Best practice setup

While Amazon Q Developer operational investigations will continue to analyze telemetry data and provide suggestions without the following features enabled, in order to ensure optimal quality and performance for Amazon Q Developer operational investigations, we highly recommend to complete the following steps:

• ¹For both Amazon EC2 and Amazon EBS, update your CloudWatch agent to version 1.30049.1 or later. For more information, see Collect metrics, logs, and traces with the CloudWatch agent.

• ²For both Amazon ECS and Amazon EKS, enable CloudWatch Container Insights. For more information, see Container Insights.

• We recommend that you enable CloudWatch Application Signals and X-Ray. For more information, see Application Signals and What is AWS X-Ray.