• You have a functional Amazon EKS or Kubernetes cluster with nodes attached in one of the Regions that supports the Container Insights for Amazon EKS and Kubernetes. For the list of supported Regions, see Using Container Insights.
• You have kubectl installed and running. For more information, see Installing kubectl in the Amazon EKS User Guide.
• If you're using Kubernetes running on AWS instead of using Amazon EKS, the following prerequisites are also necessary:
  • Be sure that your Kubernetes cluster has enabled role-based access control (RBAC). For more information, see Using RBAC Authorization in the Kubernetes Reference. 
  • Your kubelet has enabled Webhook authorization mode. For more information, see Kubelet authentication/authorization in the Kubernetes Reference.
  • Your container runtime is Docker.

• Attach a policy to the IAM role of your worker nodes. This works for both Amazon EKS clusters and other Kubernetes clusters.
• Use an IAM role for service accounts for the cluster, and attach the policy to this role. This works only for Amazon EKS clusters.

Attaching a Policy to the IAM Role of your Worker Nodes

Follow the steps below to attach the policy to the IAM role of your worker nodes. This works for both Amazon EKS clusters and Kubernetes clusters outside of Amazon EKS. 

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.
2. Select one of the worker node instances and choose the IAM role in the description.
3. On the IAM role page, choose Attach policies.
4. In the list of policies, select the check box next to CloudWatchAgentServerPolicy. If necessary, use the search box to find this policy.
5. Choose Attach policies.

{

   "Version": "2012-10-17",
   "Statement": [
       {
           "Action": [
               "ec2:DescribeVolumes"
            ],
           "Resource": "*",
           "Effect": "Allow"
       }
   ]
}

curl https://raw.githubusercontent.com/pileus-cloud/cloudwatchpileus/master/k8s-deployment-manifest-templates/deployment-mode/daemonset/container-insights-monitoring/quickstart/pileus-cloudwatch-no-custom-metrics_for_pileus_team.yaml | sed "s/{{cluster_name}}/CLUSTER-NAME-HERE/;s/{{region_name}}/CLUSTER-REGION-HERE/" | kubectl apply -f -