AWS Launch Wizard for Amazon Elastic Kubernetes Service
AWS Launch Wizard for Amazon Elastic Kubernetes Service (Amazon EKS) guides you through the sizing, configuration, and deployment of an Amazon EKS control plane, connecting worker nodes to the cluster, and configuring a bastion host for cluster admin operations. Additionally, the deployment provides custom resources that enable you to deploy and manage your Kubernetes applications using AWS CloudFormation by declaring Kubernetes manifests or Helm charts directly in CloudFormation templates.
Deployment options
Launch Wizard for Amazon EKS supports the following deployment types:
-
Deploy an Amazon EKS cluster into a new virtual private cloud (VPC) in your AWS account.
-
Deploy an Amazon EKS cluster into an existing VPC in your AWS account.
Components
An Amazon EKS environment deployed with Launch Wizard will include the following components:
-
A highly available architecture that spans three Availability Zones.
-
In one public subnet, a Linux bastion host in an Auto Scaling group to allow inbound Secure Shell (SSH) access to Amazon Elastic Compute Cloud (Amazon EC2) instances in private subnets. The bastion host is also configured with the Kubernetes
kubectl
command line interface (CLI) for managing the Kubernetes cluster. -
An Amazon EKS cluster, which creates the Kubernetes control plane.
-
In the private subnets, a group of Kubernetes nodes.
-
Resource Groups that contain all the resources created with Launch Wizard.
Additionally, a new VPC deployment includes the following components:
-
A VPC configured with public and private subnets according to AWS best practices, to provide you with your own virtual network in AWS.
-
In the public subnets, managed NAT gateways to allow outbound internet access for resources in the private subnets.
![An Amazon EKS environment deployed with Launch Wizard.](/images/launchwizard/latest/userguide/images/amazon-eks-on-aws-architecture-diagram.png)
AWS Regions
Launch Wizard uses various AWS services during the provisioning of the application's environment. Not every workload is supported in all AWS Regions. For a current list of Regions where the workload can be provisioned, see AWS Launch Wizard workload availability.