--- title_tag: Deploy a Managed Kubernetes Cluster to AWS title: Kubernetes Cluster on AWS layout: template meta_desc: Easily deploy a managed Kubernetes cluster on AWS with Pulumi and Amazon EKS using this template. meta_image: meta.png card_desc: Deploy a Kubernetes cluster on AWS with Pulumi and Amazon EKS. template: prefix: kubernetes-aws dirname: my-k8s-cluster languages: - typescript - python - go - csharp - yaml cloud: name: Amazon Web Services slug: aws --- The Kubernetes Cluster template creates an infrastructure as code project in your favorite language and deploys a managed Kubernetes cluster to AWS. The architecture includes a VPC with public and private subnets and deploys an [Amazon EKS cluster](/registry/packages/eks/api-docs/cluster/) that provides a managed Kubernetes control plane. Kubernetes worker nodes are deployed on private subnets for improved security. Load balancers created by workloads deployed on the EKS cluster will be automatically created in the public subnets. The template generates a complete infrastructure as code program to give you a working project out of the box that you can customize easily and extend to suit your needs. ![An architecture diagram of the Pulumi AWS Kubernetes template](./architecture.png) ## Using this template To use this template to deploy your own managed Kubernetes cluster, make sure you've [installed Pulumi](/docs/install/) and [configured your AWS credentials](/registry/packages/aws/installation-configuration#credentials), then create a new [project](/docs/concepts/projects/) using the template in your language of choice: {{< templates/pulumi-new >}} Follow the prompts to complete the new-project wizard. When it's done, you'll have a complete Pulumi project that's ready to deploy and configured with the most common settings. Feel free to inspect the code in {{< langfile >}} for a closer look. ## Deploying the project The template requires no additional configuration. Once the new project is created, you can deploy it immediately with [`pulumi up`](/docs/cli/commands/pulumi_up): ```bash $ pulumi up ``` When the deployment completes, Pulumi exports the following [stack output](/docs/concepts/stack#outputs) values: kubeconfig : The cluster's kubeconfig file which you can use with `kubectl` to access and communicate with your clusters. vpcId : The ID for the VPC that your cluster is running in. Output values like these are useful in many ways, most commonly as inputs for other stacks or related cloud resources. ## Customizing the project Projects created with the Kubernetes template expose the following [configuration](/docs/concepts/config/) settings: minClusterSize : The minimum number of nodes to allow in the cluster. Defaults to `3`. maxClusterSize : The maximum number of nodes to allow in the cluster. Defaults to `6`. desiredClusterSize : The desired number of nodes in the cluster. Defaults to `3`. eksNodeInstanceType : The EC2 instance type to use for the nodes. Defaults to `t2.medium`. vpcNetworkCidr : The network CIDR to use for the VPC. Defaults to `10.0.0.0/16`. All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, `Pulumi.dev.yaml`). or by changing their values with [`pulumi config set`](/docs/cli/commands/pulumi_config_set). ## Tidying up You can cleanly destroy the stack and all of its infrastructure with [`pulumi destroy`](/docs/cli/commands/pulumi_destroy): ```bash $ pulumi destroy ``` ## Learn more Congratulations! You're now well on your way to managing a production-grade Kubernetes cluster on AWS with Pulumi infrastructure as code --- and there's lots more you can do from here: * Discover more architecture templates in [Templates →](/templates) * Dive into the API docs to explore the [Amazon EKS package](/registry/packages/eks/) or [AWSx (Crosswalk) package](/registry/packages/awsx) * Expand your understanding of how Pulumi works in [Learn Pulumi →](/learn) * Read up on the latest new features [in the Pulumi Blog →](/blog/tag/kubernetes)