How do I turn on Container Insights metrics on an EKS cluster?
I want to configure Amazon CloudWatch Container Insights to see my Amazon Elastic Kubernetes Service (Amazon EKS) cluster metrics.
"I want to configure Amazon CloudWatch Container Insights to see my Amazon Elastic Kubernetes Service (Amazon EKS) cluster metrics.Short descriptionWhen used with Amazon EKS, Container Insights uses a containerized version of the CloudWatch agent to find all the containers running in a cluster. Container Insights also uses AWS Distro for OpenTelemetry (ADOT) Collector to find containers in a cluster. Then, it collects performance data at every layer of the performance stack, such as performance log events that use an embedded metric format. Afterward, it sends this data to CloudWatch Logs under the /aws/containerinsights/cluster-name/performance log group where CloudWatch creates aggregated metrics at the cluster, node, and pod levels. Container Insights also supports collecting metrics from clusters that are deployed on AWS Fargate for Amazon EKS. For more information, see Using Container Insights.Note: Container Insights is supported only on Linux instances. Amazon provides a CloudWatch agent container image on Amazon Elastic Container Registry (Amazon ECR). For more information, see cloudwatch-agent on Amazon ECR.ResolutionPrerequisitesBefore starting, review the following prerequisites:Make sure that your Amazon EKS cluster is running with nodes in the Ready state and the kubectl command is installed and running.Make sure that the AWS Identity and Access Management (IAM) managed CloudWatchAgentServerPolicy activates your Amazon EKS worker nodes to send metrics and logs to CloudWatch. To activate your worker nodes, attach a policy to the worker nodes' IAM role. Or, use an IAM role for service accounts for the cluster, and attach the policy to this role. For more information, see IAM roles for service accounts.Make sure that you're running a cluster that supports Kubernetes version 1.18 or higher. This is a requirement of Container Insights for EKS Fargate. Also, make sure that you define a Fargate profile to schedule pods on Fargate.Make sure that the Amazon EKS pod execution IAM role allows components that run on the Fargate infrastructure to make calls to AWS APIs on your behalf. For example, pulling container images from Amazon ECR.Set up Container Insights metrics on your EKS EC2 cluster using the CloudWatch agentThe CloudWatch agent or ADOT creates a log group that's named aws/containerinsights/Cluster_Name/performance and sends the performance log events to this log group.When setting up Container Insights to collect metrics, you must deploy the CloudWatch agent container image as a DaemonSet from Docker Hub. By default, this is done as an anonymous user. This pull might be subject to a rate limit.1.    If you don't have a namespace called amazon-cloudwatch, then create one:kubectl apply -f https://raw.githubusercontent.com/aws-samples/amazon-cloudwatch-container-insights/latest/k8s-deployment-manifest-templates/deployment-mode/daemonset/container-insights-monitoring/cloudwatch-namespace.yaml2.    Create a service account for the CloudWatch agent that's named cloudwatch-agent:kubectl apply -f https://raw.githubusercontent.com/aws-samples/amazon-cloudwatch-container-insights/latest/k8s-deployment-manifest-templates/deployment-mode/daemonset/container-insights-monitoring/cwagent/cwagent-serviceaccount.yaml3.    Create a configmap as a configuration file for the CloudWatch agent:ClusterName=<my-cluster-name>curl https://raw.githubusercontent.com/aws-samples/amazon-cloudwatch-container-insights/latest/k8s-deployment-manifest-templates/deployment-mode/daemonset/container-insights-monitoring/cwagent/cwagent-configmap.yaml | sed 's/cluster_name/'${ClusterName}'/' | kubectl apply -f -Note: Replace my-cluster-name with the name of your EKS cluster. To further customize the CloudWatch agent configuration, see Create a ConfigMap for the CloudWatch agent.4.    Deploy the cloudwatch-agent DaemonSet:kubectl apply -f https://raw.githubusercontent.com/aws-samples/amazon-cloudwatch-container-insights/latest/k8s-deployment-manifest-templates/deployment-mode/daemonset/container-insights-monitoring/cwagent/cwagent-daemonset.yamlOptional: To pull the CloudWatch agent from the Amazon Elastic Container Registry, patch the cloudwatch-agent DaemonSet:kubectl patch ds cloudwatch-agent -n amazon-cloudwatch -p \ '{"spec":{"template":{"spec":{"containers":[{"name":"cloudwatch-agent","image":"public.ecr.aws/cloudwatch-agent/cloudwatch-agent:latest"}]}}}}'Note: The Cloudwatch-agent Docker image on Amazon ECR supports the ARM and AMD64 architectures. Replace the latest image tag based on the image version and architecture. For more information, see images tags cloudwatch-agent on Amazon ECR.5.    For IAM roles for service accounts, create an OIDC provider and an IAM role and policy. Then, associate the IAM role to the cloudwatch-agent service account:kubectl annotate serviceaccounts cloudwatch-agent -n amazon-cloudwatch "eks.amazonaws.com/role-arn=arn:aws:iam::ACCOUNT_ID:role/IAM_ROLE_NAME"Note: Replace ACCOUNT_ID with your account ID and IAM_ROLE_NAME with the IAM role that you use for the service accounts.Troubleshoot the CloudWatch agent1.    Run the following command to retrieve the list of pods:kubectl get pods -n amazon-cloudwatch2.    Run the following command to check the events at the bottom of the output:kubectl describe pod pod-name -n amazon-cloudwatch3.    Runt the following command to check the logs:kubectl logs pod-name -n amazon-cloudwatch4.    If you see a CrashLoopBackOff error for the CloudWatch agent, then make sure that your IAM permissions are set correctly.For more information, see Verify prerequisites.Delete the CloudWatch AgentTo delete the Cloudwatch agent, run the following command:kubectl delete -f https://raw.githubusercontent.com/aws-samples/amazon-cloudwatch-container-insights/latest/k8s-deployment-manifest-templates/deployment-mode/daemonset/container-insights-monitoring/cloudwatch-namespace.yamlNote: Deleting the namespace also deletes the associated resources.Set up Container Insights metrics on your EKS EC2 cluster using ADOT1.    Run the following command to deploy the ADOT Collector as a DaemonSet:curl https://raw.githubusercontent.com/aws-observability/aws-otel-collector/main/deployment-template/eks/otel-container-insights-infra.yaml | kubectl apply -f -For more customizations, see Container Insights EKS infrastructure metrics.2.    Run the following command to confirm that the collector is running:kubectl get pods -l name=aws-otel-eks-ci -n aws-otel-eks3.    Optional: By default, the aws-otel-collector image is pulled from Docker Hub as an anonymous user. This pull might be subject to a rate limit. To pull the aws-otel-collector docker image on Amazon ECR, patch aws-otel-eks-ci DaemonSet:kubectl patch ds aws-otel-eks-ci -n aws-otel-eks -p \'{"spec":{"template":{"spec":{"containers":[{"name":"aws-otel-collector","image":"public.ecr.aws/aws-observability/aws-otel-collector:latest"}]}}}}'Note: The Cloudwatch-agent Docker image on Amazon ECR supports the ARM and AMD64 architectures. Replace the latest image tag based on the image version and architecture. For more information, see images tags cloudwatch-agent on Amazon ECR.5.    Optional: For IAM roles for service accounts, create an OIDC provider and an IAM role and policy. Then, associate the IAM role to the aws-otel-sa service account.kubectl annotate serviceaccounts aws-otel-sa -n aws-otel-eks "eks.amazonaws.com/role-arn=arn:aws:iam::ACCOUNT_ID:role/IAM_ROLE_NAME"Note: Replace ACCOUNT_ID with your account ID and IAM_ROLE_NAME with the IAM role that you use for the service accounts.Delete ADOTTo delete ADOT, run the following command:curl https://raw.githubusercontent.com/aws-observability/aws-otel-collector/main/deployment-template/eks/otel-container-insights-infra.yaml |kubectl delete -f -Set up Container Insights metrics on an EKS Fargate cluster using ADOTFor applications that run on Amazon EKS and AWS Fargate, you can use ADOT to set up Container Insights. EKS Fargate networking architecture doesn’t allow pods to directly reach the kubelet on the worker to retrieve resource metrics. The ADOT Collector calls the Kubernetes API server to proxy the connection to the kubelet on a worker node. It then collects kubelet’s advisor metrics for workloads on that node.Note: A single instance of ADOT Collector isn't sufficient to collect resource metrics from all the nodes in a cluster.The ADOT Collector sends the following metrics to CloudWatch for every workload that runs on EKS Fargate:pod_cpu_utilization_over_pod_limitpod_cpu_usage_totalpod_cpu_limitpod_memory_utilization_over_pod_limitpod_memory_working_setpod_memory_limitpod_network_rx_bytespod_network_tx_bytesEach metric is associated with the following dimension sets and collected under the CloudWatch namespace that's named ContainerInsights:ClusterName, LaunchTypeClusterName, Namespace, LaunchTypeClusterName, Namespace, PodName, LaunchTypeFor more details, see Container Insights EKS Fargate.To deploy ADOT in your EKS Fargate, complete the following steps:1.    Associate a Kubernetes service account with an IAM role. Create an IAM role that's named EKS-ADOT-ServiceAccount-Role that's associated with a Kubernetes service account that's named adot-collector. The following helper script requires eksctl:#!/bin/bashCLUSTER_NAME=YOUR-EKS-CLUSTER-NAMEREGION=YOUR-EKS-CLUSTER-REGIONSERVICE_ACCOUNT_NAMESPACE=fargate-container-insightsSERVICE_ACCOUNT_NAME=adot-collectorSERVICE_ACCOUNT_IAM_ROLE=EKS-Fargate-ADOT-ServiceAccount-RoleSERVICE_ACCOUNT_IAM_POLICY=arn:aws:iam::aws:policy/CloudWatchAgentServerPolicyeksctl utils associate-iam-oidc-provider \--cluster=$CLUSTER_NAME \--approveeksctl create iamserviceaccount \--cluster=$CLUSTER_NAME \--region=$REGION \--name=$SERVICE_ACCOUNT_NAME \--namespace=$SERVICE_ACCOUNT_NAMESPACE \--role-name=$SERVICE_ACCOUNT_IAM_ROLE \--attach-policy-arn=$SERVICE_ACCOUNT_IAM_POLICY \--approveNote: Replace CLUSTER_NAME with your cluster name and REGION with your AWS Region.2.    Run the following command to deploy the ADOT Collector as a Kubernetes StatefulSet:ClusterName=<my-cluster-name>Region=<my-cluster-region>curl https://raw.githubusercontent.com/aws-observability/aws-otel-collector/main/deployment-template/eks/otel-fargate-container-insights.yaml | sed 's/YOUR-EKS-CLUSTER-NAME/'${ClusterName}'/;s/us-east-1/'${Region}'/' | kubectl apply -f -Note: Make sure that you have a matching fargate profile to provision the StatefulSet pods on AWS Fargate. Replace my-cluster-name with your cluster's name and my-cluster-region with the Region that your cluster is located in.3.    Run the following command to verify that the ADOT Collector pod is running:kubectl get pods -n fargate-container-insights4.    Optional: By default, the aws-otel-collector image is pulled from Docker Hub as an anonymous user. This pull might be subject to a rate limit. To pull the aws-otel-collector Docker image on Amazon ECR, patch adot-collector StatefulSet:kubectl patch sts adot-collector -n fargate-container-insights -p \'{"spec":{"template":{"spec":{"containers":[{"name":"adot-collector","image":"public.ecr.aws/aws-observability/aws-otel-collector:latest"}]}}}}'Delete ADOTTo delete ADOT, run the following command:eksctl delete iamserviceaccount —cluster CLUSTER_NAME —name adot-collectorClusterName=<my-cluster-name>Region=<my-cluster-region>curl https://raw.githubusercontent.com/aws-observability/aws-otel-collector/main/deployment-template/eks/otel-fargate-container-insights.yaml | sed 's/YOUR-EKS-CLUSTER-NAME/'${ClusterName}'/;s/us-east-1/'${Region}'/' | kubectl delete -f -Related informationUsing Container InsightsFollow"