During this year’s re:Invent, Amazon announced Amazon EKS Distro (EKS-D), a Kubernetes distribution based on and used by Amazon EKS. We’re happy to announce that Epsagon is completely compatible with EKS-D.

What is Amazon EKS Distro?

EKS-D enables users to create reliable and secure Kubernetes clusters using the same versions of Kubernetes and its dependencies deployed by Amazon EKS. Each EKS-D release follows the EKS process, verifying new Kubernetes versions for compatibility. The EKS-D source code, open-source tooling, binaries, and container images as well as configuration are provided for reproducible builds via public Git and S3 storage locations.

With EKS-D, Amazon provides extended support for Kubernetes versions after community support expires, providing updated builds of previous versions including the latest security patches.

How does EKS-D affect EKS monitoring using Epsagon?

EKS-D offers a secure and sustainable Kubernetes distro on EKS. Monitoring-wise, EKS-D would not have any effect on what you can currently monitor with Epsagon. You can still easily integrate EKS without any additional configuration.

With Epsagon, you will still be able to monitor control plane metrics (API server latencies, etcd latencies, etc.), cluster state metrics (kube-state-metrics), resource metrics (pod request limits, node capacity, etc.) as well as leverage the power of AWS CloudWatch and Prometheus.

Kubernetes Monitoring in Epsagon

Figure 1: Kubernetes Monitoring in Epsagon

Observability within Amazon EKS

Kubernetes clusters, deployments, pods, and containers, as you know, can be hard to configure and maintain. Epsagon leverages the power of Prometheus (without the need to manage or provision it) to provide best-in-class monitoring and alerting with an extensive experience and user interface.

Epsagon’s observability platform provides an automated correlation of traces, metrics, and logs within a single dashboard. The correlation between the application-level tracing and the infrastructure-level metrics enables developers to see a cluster or a pod and go right to the relevant traces, without tedious and time-consuming searches through hundreds, even thousands of logs, to identify issues and their sources.

Conclusion

With EKS-D, EKS users will have a hassle-free Kubernetes experience and, leveraging Epsagon, will also be well-equipped to instantly monitor, troubleshoot, and trace issues within EKS.

Read More: 

A Complete Guide to Monitoring Amazon EKS

Amazon EKS Distro

AWS CloudWatch Metrics and Dashboards