---
title: Amazon EKS Anywhere
description: An EKS deployment option for operating Kubernetes clusters on-premises
breadcrumbs: Docs > Integrations > Amazon EKS Anywhere
---

# Amazon EKS Anywhere
Supported OS Integration version1.0.0
## Overview{% #overview %}

Amazon Elastic Kubernetes Service (EKS) is a managed Kubernetes service that automates certain aspects of deployment and maintenance for any standard Kubernetes environment. Whether you are migrating an existing Kubernetes application to Amazon EKS, or deploying a new cluster on Amazon EKS on AWS Outposts, Datadog helps you monitor your EKS environments in real time.

[Amazon EKS Anywhere](https://aws.amazon.com/eks/eks-anywhere/) is a deployment option that enables you to create and operate Kubernetes clusters on-premises, including virtual machines (for example, VMware vSphere) and bare metal servers.

## Setup{% #setup %}

Because Datadog already integrates with Kubernetes and AWS, it is ready-made to monitor EKS. If you're running the Agent in a Kubernetes cluster and plan to migrate to EKS, you can continue monitoring your cluster with Datadog.

Additionally, [Amazon EKS Managed Node Groups](https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html) and [Amazon EKS on AWS Outposts](https://docs.aws.amazon.com/eks/latest/userguide/eks-on-outposts.html) are supported.

### Datadog Helm chart configuration{% #datadog-helm-chart-configuration %}

Use the [Agent deployment instructions with Helm](https://docs.datadoghq.com/agent/kubernetes/?tab=helm#installation) with these additional configuration instructions:

1. Set `datadog.kubelet.tlsVerify` to `false`.
1. Set a toleration on the Agent pod. This is necessary for monitoring the control plane.

The following Helm snippet demonstrates the specific changes for monitoring EKS Anywhere:

```yaml
datadog:
  kubelet:
    tlsVerify: false
agents:
  tolerations:
  - effect: NoSchedule
    key: node-role.kubernetes.io/master
    operator: Exists
```

### Metric collection{% #metric-collection %}

Monitoring EKS requires setting up one of the following Datadog integrations along with integrations for any other AWS services you're running with EKS, such as [ELB](https://docs.datadoghq.com/integrations/amazon_elb/).

- [Kubernetes](https://docs.datadoghq.com/integrations/kubernetes/)
- [AWS](https://docs.datadoghq.com/integrations/amazon_web_services/)
- [AWS EC2](https://docs.datadoghq.com/integrations/amazon_ec2/)

### Log collection{% #log-collection %}

*Available for Agent versions >6.0*

The setup is exactly the same as for Kubernetes. To start collecting logs from all your containers, use your Datadog Agent [environment variables](https://docs.datadoghq.com/agent/basic_agent_usage/kubernetes/#log-collection-setup).

Use DaemonSets to [automatically deploy the Datadog Agent on all of your nodes](https://docs.datadoghq.com/agent/basic_agent_usage/kubernetes/#container-installation).

Follow the [container log collection instructions](https://docs.datadoghq.com/logs/log_collection/docker/#option-2-container-installation) to learn more about environment variables and advanced setup options.

## Troubleshooting{% #troubleshooting %}

Need help? Contact [Datadog support](https://docs.datadoghq.com/help/).

## Further Reading{% #further-reading %}

- [Monitor Amazon EKS with Datadog](https://www.datadoghq.com/blog/announcing-eks)
- [Key metrics for Amazon EKS monitoring](https://www.datadoghq.com/blog/eks-cluster-metrics)
- [Amazon EKS on AWS Fargate](https://docs.datadoghq.com/integrations/eks_fargate/)