Private Cluster - VPC endpoint creation error

[somasuntaram15]

Hi Everyone,

I’m facing an issue while creating a private EKS cluster using eksctl, where it automatically creates the necessary VPC endpoints. During the process, I encountered the following error:

Error: Found another VPC endpoint subnet in the availability zone of subnet-xxxxxx. VPC endpoint subnets should be in different availability zones supported by the VPC endpoint service.

I understand that for private EKS clusters, eksctl automatically provisions VPC endpoints (e.g., for S3, EC2, ECR, STS) to enable communication with AWS services without public internet access. However, the subnets in my VPC are configured such that there are multiple private subnets in each Availability Zone (AZ), and it seems eksctl is selecting subnets in the same AZ for the VPC endpoints, causing the conflict.

How to handle this in configurations with multiple private subnets per AZ?

Looking forward to your thoughts and suggestions. Thanks!

[github-actions]

Hello somasuntaram15 👋 Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website