-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(eks): support AccessConfig for the Cluster construct #1027
Comments
+1 also interested in migrating to access entries. |
Note: Half of the work to do this seems to have been done already :) The "AuthenticationMode" half looks done: (as of EKS Blueprints version 1.15.1)
The "AccessConfig" 2nd half, looks to be WIP: That said, it looks like a workaround method should exist here: |
Actually, this whole feature seems to be available in eks-cdk-blueprints v1.15.1, :) just not yet documented. (wait technically it doesn't exist in Cluster construct, but it seems to be available via a different construct/methodology.)
|
I'm also interested in this existing |
For those interested this is possible via an ancillary stack. We have a few things being deployed with the bleuprint which this fit nicely into. Hope it helps. Perform a cluster lookup
Then simply implement the access policies and entries.
|
Describe the feature
Provide option for Amazon EKS access management controls.
The
AuthenticationMode
supportsCONFIG_MAP
, which is the default,API_AND_CONFIG_MAP
andCONFIG_MAP
. It allows users to switch the mode on cluster creation or update. When the mode has API support, users have to define the AccessEntry to map the access policies and the IAM principalsFurthermore, provide option to support create
AccessEntry
eitherRef: aws/aws-cdk#30016
Use Case
Provide option for selecting
AuthenticationMode
and createAccessEntry
Proposed Solution
No response
Other Information
No response
Acknowledgements
CDK version used
2.147.0
EKS Blueprints Version
1.14.1
Node.js Version
v22.1.0
Environment details (OS name and version, etc.)
macOS Sonoma 14.5
The text was updated successfully, but these errors were encountered: