You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should provide guidance on EKS access management using AWS IAM Identity Center (formerly AWS SSO). This blog post (https://aws.amazon.com/blogs/containers/a-quick-path-to-amazon-eks-single-sign-on-using-aws-sso/) is outdated and has limitations that aren't mentioned, particularly around the IAM role ARN generated by Identity Center having a random suffix which makes it impractical to use.
Create a new section covering options for EKS access management
Include comparison of different approaches with their trade-offs:
IAM Identity Center + EKS CAM APIs
Direct IAM Users/Roles Mapped to EKS RBAC
OpenID Connect (OIDC) Providers
IRSA/Pod Identity/etc
Document known limitations and considerations for each method
We should provide guidance on EKS access management using AWS IAM Identity Center (formerly AWS SSO). This blog post (https://aws.amazon.com/blogs/containers/a-quick-path-to-amazon-eks-single-sign-on-using-aws-sso/) is outdated and has limitations that aren't mentioned, particularly around the IAM role ARN generated by Identity Center having a random suffix which makes it impractical to use.
Related:
The text was updated successfully, but these errors were encountered: