Setup Container Insights

If you came to this page directly, you will have to setup the application environment to proceed with this module. Go to Environment Setup to setup the environment and come back here again.

We will be following the instructions from here to setup Container Insights on the EKS cluster.

As you are already aware, the front end web application is hosted on an EKS cluster.

Architecture

Below is the architecture that shows the components that are involved in collecting logs and metrics from your EKS environment.

Architecture

Deploy Container Insights on the cluster

kubectl apply -f ./resources/cwagent-fluentd-quickstart.yaml

Execute the following command to check that the cloudwatch and fluentd agents have been installed properly.

kubectl get pods -A

Your output should be similar to the one below.

NAMESPACE           NAME                                  READY   STATUS    RESTARTS   AGE
amazon-cloudwatch   cloudwatch-agent-4kn6k                1/1     Running   0          18s
amazon-cloudwatch   cloudwatch-agent-74fkh                1/1     Running   0          18s
amazon-cloudwatch   fluentd-cloudwatch-ht72x              1/1     Running   0          18s
amazon-cloudwatch   fluentd-cloudwatch-pmc98              1/1     Running   0          18s
default             petsite-deployment-6fc674cc47-8brkp   1/1     Running   0          79s
default             petsite-deployment-6fc674cc47-sqk96   1/1     Running   0          79s
default             xray-daemon-drz9v                     1/1     Running   0          47m
default             xray-daemon-hgjrh                     1/1     Running   0          47m
kube-system         aws-node-dl4mz                        1/1     Running   0          52m
kube-system         aws-node-njk4d                        1/1     Running   0          52m
kube-system         coredns-5fb4bd6df8-5fdjd              1/1     Running   0          58m
kube-system         coredns-5fb4bd6df8-5ndm2              1/1     Running   0          58m
kube-system         kube-proxy-jklws                      1/1     Running   0          52m
kube-system         kube-proxy-rqc48                      1/1     Running   0          52m