AWS services where investigations are supported - Amazon CloudWatch

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 only in the US East (N. Virginia) Region.

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 EC21

  • Amazon ECS on Amazon EC22

  • Amazon ECS on Fargate2

  • Amazon EKS2

  • Amazon DynamoDB

  • Amazon S3

  • Amazon EBS1

  • 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: