Outdated EKS authentication method in answer

[Azamjon]

A company needs to accelerate the performance of its AI-powered medical diagnostic application by running its machine learning workloads on the edge of telecommunication carriers’ 5G networks. The application must be deployed to a Kubernetes cluster and have role-based access control (RBAC) access to IAM users and roles for cluster authentication.

I noticed that the correct answer uses the aws-auth ConfigMap to provide IAM user/role access to the EKS cluster.

According to the current AWS documentation, the aws-auth ConfigMap is deprecated, and AWS recommends using EKS Access Entries / Cluster Access Management for managing IAM principal access to EKS.

Could you please update this question to reflect the current EKS authentication method, or clarify that aws-auth is the legacy approach?

[JR-TutorialsDojo]

Hello Azam2,

Thank you for bringing this to our attention.

You are correct that the aws‑auth ConfigMap is now considered a legacy approach for granting IAM user and role access to Amazon EKS clusters. AWS currently recommends using EKS Access Entries / Cluster Access Management as the preferred method for managing IAM principal access.

We will make the necessary updates, and you should see them reflected on the portal soon. We appreciate your diligence in helping us keep our content accurate and up to date. Please feel free to share any other observations you may have.

Best regards,
JR @ Tutorials Dojo