Amazon CloudWatch
User Guide

Using Container Insights

CloudWatch Container Insights is in open preview. The preview is open to all AWS accounts and you do not need to request access. Features may be added or changed before announcing General Availability. Don’t hesitate to contact us with any feedback or let us know if you would like to be informed when updates are made by emailing us at containerinsightsfeedback@amazon.com

On August 20, 2019, we updated the Container Insights for Amazon EKS and Kubernetes preview with additional dimensions for Container Insights pod, service and node metrics. If you are using Container Insights with Amazon EKS or Kubernetes, you must update the containerized CloudWatch agent container image by following the directions in Updating the CloudWatch Agent Container Image. Alarms and custom dashboards that reference the previous metrics must be manually updated.

If you use Amazon Elastic Container Service, Amazon Elastic Kubernetes Service, or other Kubernetes platforms on Amazon EC2, you can use CloudWatch Container Insights to collect, aggregate, and summarize metrics and logs from your containerized applications and microservices. The metrics include utilization for resources such as CPU, memory, disk, and network. Container Insights also provides diagnostic information, such as container restart failures, to help you isolate issues and resolve them quickly. You can also set CloudWatch alarms on metrics that Container Insights collects.

The metrics that Container Insights collects are available in CloudWatch automatic dashboards. You can view further container data with CloudWatch Logs Insights.

Operational data is collected as performance log events. These are entries that use a structured JSON schema that enables high-cardinality data to be ingested and stored at scale. From this data, CloudWatch creates higher-level aggregated metrics at the cluster, node, pod, task, and service level as CloudWatch metrics.

On Amazon EKS and Kubernetes, Container Insights uses a containerized version of the CloudWatch agent to discover all the running containers in a cluster and collect performance data at every layer of the performance stack.

Currently, Container Insights isn't supported on AWS Batch.

Container Insights supports encryption with Customer Master Key (CMK) for the logs and metrics that it collects. To enable this encryption, you must manually enable KMS encryption for the log group that receives Container Insights data. This results in Container Insights encrypting this data using the provided CMK. For more information, see Encrypt Log Data in CloudWatch Logs Using AWS KMS.

Supported Regions for Amazon ECS

This preview release supports Container Insights on Amazon ECS in the following Regions:

  • US East (N. Virginia)

  • US East (Ohio)

  • US West (N. California)

  • US West (Oregon)

  • Canada (Central)

  • EU (Frankfurt)

  • EU (Ireland)

  • EU (London)

  • EU (Paris)

  • Asia Pacific (Tokyo)

  • Asia Pacific (Seoul)

  • Asia Pacific (Singapore)

  • Asia Pacific (Sydney)

  • Asia Pacific (Mumbai)

  • South America (São Paulo)

AWS Fargate is not supported in EU (Paris) or South America (São Paulo).

Supported Regions for Amazon EKS and Kubernetes

This preview release supports Container Insights on Amazon EKS and Kubernetes in the following Regions:

  • US East (N. Virginia)

  • US East (Ohio)

  • US West (N. California)

  • US West (Oregon)

  • Canada (Central)

  • EU (Frankfurt)

  • EU (Ireland)

  • EU (London)

  • EU (Paris)

  • Asia Pacific (Mumbai)

  • Asia Pacific (Singapore)

  • Asia Pacific (Sydney)

  • Asia Pacific (Tokyo)

  • Asia Pacific (Seoul)

  • South America (São Paulo)