Скачать или смотреть Resolving the AWS-CDK EKS Cluster Creation Issue: No Private Subnets Needed!

Discover how to create an EKS cluster with AWS CDK without requiring private subnets, thus avoiding unnecessary costs. Learn the steps and code setup in our in-depth guide!
---
This video is based on the question https://stackoverflow.com/q/63595963/ asked by the user 'user3909893' ( https://stackoverflow.com/u/3909893/ ) and on the answer https://stackoverflow.com/a/63605105/ provided by the user 'user3909893' ( https://stackoverflow.com/u/3909893/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: AWS-CDK EKS Cluster can not be created in a VPC without at least 1 private subnet

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Introduction

Building an Amazon EKS (Elastic Kubernetes Service) cluster using the AWS Cloud Development Kit (CDK) is a powerful way to manage containerized applications. However, many developers run into an issue when trying to define a Virtual Private Cloud (VPC) exclusively with public subnets. The error message can be perplexing:

[[See Video to Reveal this Text or Code Snippet]]

This error arises when the AWS CDK expects at least one private subnet for the cluster creation. In this post, we'll break down how to resolve this issue and allow you to instantiate an EKS cluster without needing those private subnets.

Understanding the Problem

While you may want to set up an EKS cluster in a simplified environment that only uses public subnets, AWS CDK enforces certain structural requirements. By default, the eks.Cluster initialization requires both public and private subnets. This can lead to unnecessary costs, as provisioning private subnets incurs additional charges which you might not need.

Solution: Creating a Custom EKS Cluster Configuration

The key to overcoming this limitation is to specify the subnets explicitly through the vpcSubnets parameter in the eks.Cluster constructor. Here’s how to do it step-by-step:

Step 1: Define Your VPC

First, you create your VPC without any private subnets. Ensure your setup looks similar to this:

[[See Video to Reveal this Text or Code Snippet]]

In the above definition, we are explicitly defining two public subnets and no private ones.

Step 2: Initialize the EKS Cluster with Public Subnets

When you instantiate the EKS cluster, set the vpcSubnets to specify that you only want the public subnets:

TypeScript Example

If you are using TypeScript for your CDK project, your cluster instantiation would look like this:

[[See Video to Reveal this Text or Code Snippet]]

Python Example

For Python developers, it's just as straightforward. The code looks like this:

[[See Video to Reveal this Text or Code Snippet]]

Key Takeaways

No Need for Private Subnets: By defining the vpcSubnets parameter, you can create an EKS cluster without needing to provision private subnets, cutting down on unnecessary costs.

Flexibility in Setup: This solution gives you the flexibility to configure your EKS cluster according to your specific needs.

Conclusion

Setting up an Amazon EKS cluster with AWS CDK does not have to come with the added burden of managing private subnets. By leveraging the vpcSubnets parameter, you can efficiently design a cost-effective infrastructure tailored to your public-only requirements.

Feel free to share your thoughts or experiences with EKS or AWS CDK in the comments below!