diff --git a/README.md b/README.md
index 6fcdb3c46ab69a6ca831580bdd3b50efaabaf739..604b7e7e33fc88685f50be695a11d36412d14820 100644
--- a/README.md
+++ b/README.md
@@ -645,6 +645,7 @@ As described in the [Prerequisites](#prerequisites) section, in order to retriev
 
 If you are using Google's GKE product, see [cAdvisor support](docs/GKE-cadvisor-support.md).
 
+If you are using AWS EKS, see [AWS EKS CNI support](docs/EKS-cni-support.md)
 #### Authentication problem
 
 The Prometheus `/targets` page will show the kubelet job with the error `403 Unauthorized`, when token authentication is not enabled. Ensure, that the `--authentication-token-webhook=true` flag is enabled on all kubelet configurations.
diff --git a/docs/EKS-cni-support.md b/docs/EKS-cni-support.md
new file mode 100644
index 0000000000000000000000000000000000000000..b75b749b2479b05b5c2012de45e36e7a22ed2da0
--- /dev/null
+++ b/docs/EKS-cni-support.md
@@ -0,0 +1,22 @@
+# CNI monitoring special configuration updates for EKS
+
+AWS EKS uses [CNI](https://github.com/aws/amazon-vpc-cni-k8s) networking plugin for pod networking in Kubernetes using Elastic Network Interfaces on AWS
+
+One fatal issue that can occur is that you run out of IP addresses in your eks cluster. (Generally happens due to error configs where pods keep scheduling).
+
+You can monitor the `awscni` using kube-promethus with : 
+```
+local kp = (import 'kube-prometheus/kube-prometheus.libsonnet') +
+    (import 'kube-prometheus/kube-prometheus-aws-eks-cni.libsonnet') +
+	{
+        _config+:: {
+		# ... config here
+		}
+    };
+```
+
+After you have the required yaml file please run
+
+```
+kubectl apply -f manifests/prometheus-serviceMonitorAwsEksCNI.yaml
+```