| Info |
|---|
The article explains how to provide access to Amazon EKS Cluster for Cloudaware to discover EKS resources (pods, nodes, etc) automatically. Read more |
...
Cloudaware supports the following options of EKS access configuration based on cluster authentication mode:
Access entries
Use access entries to manage the Kubernetes permissions of IAM principals from outside the cluster.
Ensure the cluster meets one of the following requirements: a platform version that is equal to or later than listed in the table below, or a Kubernetes version that is equal to or newer than those listed. Read more
Kubernetes version | Platform version |
|---|---|
1.30 | eks.2 |
1.29 | eks.1 |
1.28 | eks.6 |
1.27 | eks.10 |
1.26 | eks.11 |
1.25 | eks.12 |
1.24 | eks.15 |
1.23 | eks.17 |
Ensure that the access entry method is enabled in AWS. Read more
Migrate existing aws-auth ConfigMap entries to access entries. Read more
aws-auth ConfigMap (legacy)
All clusters created before the introduction of access entries have the ConfigMap method enabled. Use aws-auth ConfigMap to provide Cloudaware with read access to Kubernetes API on a cluster level.
Full access
1. Ensure that the AWS credentials that Kubectl is using are already authorized for your cluster (the IAM user who created the cluster has the required permissions by default). Open the aws-auth:
...
| Note |
|---|
If the Amazon EKS Cluster is running in a private network, check this guide to install Cloudaware Breeze agent for secure connection. |
Results
Amazon Web Services → Compute → EKS