A SysOps Administrator needs to enable Amazon CloudWatch Container Insights on an existing Amazon EKS cluster that runs on Amazon EC2 worker nodes. The administrator needs to collect both container-level performance metrics and application logs, and view them on a unified dashboard. Which two actions should the SysOps Administrator take to configure this monitoring solution? (Select TWO.)
- Attach the CloudWatchAgentServerPolicy IAM managed policy to the IAM role of the Amazon EKS worker nodes.Answer
- Deploy the CloudWatch agent as a DaemonSet to collect performance metrics, and Fluent Bit as a DaemonSet to collect container logs.Answer
- CEnable detailed monitoring on the EC2 worker nodes using the Amazon EC2 console to enable container-level granular metric collection.
- DConfigure an Amazon EventBridge rule that triggers an AWS Systems Manager Automation document to dynamically push logs from the EC2 worker nodes to CloudWatch.
- EManually create the CloudWatch log groups for EKS and set their retention policy to Never Expire, as the CloudWatch agent and Fluent Bit cannot auto-create log groups.
Answer
Attach the CloudWatchAgentServerPolicy IAM managed policy to the IAM role of the Amazon EKS worker nodes, and deploy the CloudWatch agent as a DaemonSet to collect performance metrics, and Fluent Bit as a DaemonSet to collect container logs.
The correct options are attaching the CloudWatchAgentServerPolicy policy to the EKS worker nodes' IAM role, and deploying the CloudWatch agent and Fluent Bit DaemonSets. This ensures both permissions and agent workloads are properly configured on the EC2 instances supporting the cluster.
Step-by-Step Solution
Key Concept
Configuring Container Insights on EKS requires node permissions and DaemonSet configurations for the CloudWatch agent and Fluent Bit.