Introduction to EKS Blueprints
Architectural Diagram
Core concept
| Concepts | Description |
|---|---|
| Cluster | An EKS Cluster deployed following best practices. |
| Resource Provider | Resource providers are abstractions that supply external AWS resources to the cluster (e.g. hosted zones, VPCs, etc.). |
| Add-ons | Allow you to configure, deploy, and update the operational software, or add-ons, that provide key functionality to support your Kubernetes applications. |
| Teams | A logical grouping of IAM that has access to a Kubernetes namespace(s), or cluster administrative access depending upon the team type. |
| Pipelines | Continuous Delivery pipelines for deploying clusters and add-ons |
| Application | An application that runs within an EKS Cluster. |
Blueprint
EKS Blueprints allows you to configure and deploy what is called a blueprint cluster. Blueprint combines clusters, add-ons, and groups into a cohesive object that can be deployed as a whole. Once the blueprint is configured, it can be deployed easily across any number of AWS accounts and regions. Blueprints also leverages the GitOps engine to facilitate cluster startup and workload integration.