Deploying this Quick Start for a new virtual private cloud (VPC) with
default parameters builds the following {partner-product-name} environment in the
AWS Cloud.

// Replace this example diagram with your own. Send us your source PowerPoint file. Be sure to follow our guidelines here : http://(we should include these points on our contributors guide)

[#architecture1]
.Quick Start architecture for _{partner-product-name}_ on AWS
[link=images/image2.png]
image::../images/boomi-kubernetes-molecule-architecture-diagram.png[image,width=648,height=430]

The Quick Start sets up the following:

* A highly available architecture that spans three Availability Zones.*
* A VPC configured with public and private subnets according to AWS best practices, to provide you with your own virtual network on AWS.*
* A Network Load Balancer.
* In the public subnets:

** Managed NAT gateways to allow outbound internet access for resources in the private subnets.*
** 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 public and private subnets, with Amazon CloudWatch for monitoring.

* In the private subnets:

** Amazon EKS cluster with the {partner-company-name} software installed, one pod in each Availability Zone.
** Amazon Elastic File System (Amazon EFS) deployed in the Region. Three Amazon EFS mount points are created also, one in each Availability Zone.

*The template that deploys the Quick Start into an existing VPC skips the components marked by asterisks and prompts you for your existing VPC configuration.