About Deployment & Base Infrastructure
In order to provision cloud clusters, you must first deploy a base set of infrastructure into your CSP account. Throughout our documentation, we refer to this as the base infrastructure. This base infrastructure is shared by multiple clusters and varies for each CSP. In essence, you can think of it as the networking stack which clusters will be deployed on top of.
Below, you can find specific details about the implementation of this base infrastructure for each CSP.
AWS Infrastructure
Deploying base infrastructure provisions the following on AWS:
- a Virtual Private Cloud (VPC)
- an internet gateway
- public and private subnets
- public and private route tables and routes
- a Network Address Translation (NAT) gateway
- an Elastic IP address for the NAT gateway
- a Route 53 Hosted Zone
- a security group
The schematic below shows an ACTIVATE-deployed cluster in AWS Cloud.
The controller and compute nodes are shown in Availability Zone us-east-1a inside the us-east-1 Region. All compute nodes in a region use a single NAT gateway for outbound internet connectivity. This NAT gateway is pre-provisioned as part of the base infrastructure. The AMI used for the controller and compute nodes is inside the Parallel Works AWS account.
Creating a NAT gateway will result in an additional monthly charge in your AWS account. For more information, please see this AWS pricing list.
A diagram of ACTIVATE clusters in AWS Cloud
Azure Infrastructure
A diagram of ACTIVATE clusters in Azure Cloud