How awslabs/cdk-eks-blueprints works
Project type and purpose
• This is a TypeScript-based AWS CDK library (“eks‐blueprints”) that provides a prescriptive, extensible framework for provisioning and bootstrapping Amazon EKS clusters with add-ons, teams, GitOps pipelines, and operational tooling.
• It’s not a user-facing web app but an Infrastructure-as-Code (IaC) framework packaged as an NPM module. It exposes constructs, builders, plug-in add-ons, resource providers, cluster providers, and pipelines to automate the creation of fully operational EKS clusters.
File structure
• Top-level:
• bin/main.ts – example CDK entrypoint for users
• lib/ – core library code subdivided into logical modules (addons, builders, cluster-providers, pipelines, resource-providers, spi, stacks, teams, utils)
• examples/ – sample projects showing how to consume the library
• docs/ and mkdocs.yml – site documentation source
• ci/ and .github/workflows – continuous integration and documentation pipelines
• test/ – unit tests validating each add-on, provider, and utility
• Configuration: package.json, tsconfig.json, cdk.json, Makefile, devcontainer/ – developer tooling
• The “spi” directory defines extension contracts (ClusterAddOn, TeamContract, etc.), indicating a plug-in architecture.
README-driven insights
• The library uses a Builder pattern (EksBlueprint.builder()…build(app, name)) to assemble clusters with configurable add-ons, cluster providers (e.g., managed node groups, Fargate), resource providers (VPC, IAM, S3), and team namespaces/policies.
• It provisions AWS constructs via CDK → CloudFormation and then installs Kubernetes add-ons (ArgoCD, Calico, Metrics Server, etc.) into the cluster for GitOps and ops automation.