-
Notifications
You must be signed in to change notification settings - Fork 4k
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
[aws-eks] cluster to support private endpoint access #7972
Comments
Yeah the tricky part will be the lambda custom resources inside the vpc. That one will be fun! |
Hi @eladb Looks like the ClusterResourceProvider will be in a nested stack and we can't just pass the props.Vpc as
thanks |
You should technically be able to just reference the |
Let's continue the discussion over #5220... |
Resolved by #9095 |
Add
endpointPrivateAccess
support for EKS cluster creation.It's currently not possible to create an Amazon EKS cluster with private-only endpoint with AWS CDK and this gap stops some users and customers from using aws-eks construct lib to create their EKS cluster.
Use Case
To secure the cluster endpoint in private network when creating the cluster with AWS CDK.
Proposed Solution
To expose an additional property for
Cluster
resource.Will make sure the kubectl provider in Lambda with vpc support can connect to the eks private endpoint. aws-samples/aws-lambda-layer-kubectl#32
Other
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: