Skip to content

Instantly share code, notes, and snippets.

@seifrajhi

seifrajhi/aws-configmap-vs-access-entries.md

Created October 12, 2024 09:18
Show Gist options
  • Save seifrajhi/aaf19aa420d0798489bbce869da870b8 to your computer and use it in GitHub Desktop.
Save seifrajhi/aaf19aa420d0798489bbce869da870b8 to your computer and use it in GitHub Desktop.
Download ZIP
Comparison between the old ConfigMap method and the new EKS API
Raw
aws-configmap-vs-access-entries.md
Old Method: aws-auth ConfigMap New Method: EKS API
Manual Updates: Required manual editing of the aws-auth ConfigMap to manage access. Automated Management: Access entries can be managed programmatically through the EKS API.
Scalability Issues: Difficult to manage access for a large number of users and roles. Scalable: Easier to manage access for a large number of users and roles.
Risk of Misconfiguration: Errors in the ConfigMap could break access control. Reduced Risk: Less prone to errors compared to manual ConfigMap updates.
Cluster Owner Issues: The default cluster creator had full admin rights, and deleting this user could result in losing access to the cluster. Flexible Ownership: Allows changing the cluster owner and adding IAM principals by other users.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment