AWS services where investigations are supported
You can launch investigations from telemetry data (such as CloudWatch metrics, alarms, and logs), review generated anomaly signals, and explore hypotheses on investigations. CloudWatch 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. CloudWatch 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, CloudWatch investigations will attempt to infer dependency relationships through co-occurring telemetry anomalies.
Best practice setup
While CloudWatch investigations will continue to analyze telemetry data and provide suggestions without the following features enabled, in order to ensure optimal quality and performance for CloudWatch investigations, we highly recommend to complete the following steps:
-
1For 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 using the CloudWatch agent.
-
2For 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.