Network configurations - Amazon ParallelCluster
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Network configurations

Amazon ParallelCluster uses Amazon Virtual Private Cloud (VPC) for networking. VPC provides a flexible and configurable networking platform where you can deploy clusters.

The VPC must have DNS Resolution = yes, DNS Hostnames = yes and DHCP options with the correct domain name for the Region. The default DHCP Option Set already specifies the required AmazonProvidedDNS. If specifying more than one domain name server, see DHCP options sets in the Amazon VPC User Guide.

Amazon ParallelCluster supports the following high-level configurations:

  • One subnet for both head and compute nodes.

  • Two subnets, with the head node in one public subnet, and compute nodes in a private subnet. The subnets can be either new or existing ones.

All of these configurations can operate with or without public IP addressing. Amazon ParallelCluster can also be deployed to use an HTTP proxy for all Amazon requests. The combinations of these configurations result in many deployment scenarios. For example, you can configure a single public subnet with all access over the internet. Or, you can configure a fully private network using Amazon Direct Connect and HTTP proxy for all traffic.

Starting from Amazon ParallelCluster 3.0.0 it is possible to configure different SecurityGroups, AdditionalSecurityGroups and PlacementGroup settings for each queue. For more information, see HeadNode / Networking and SlurmQueues / Networking and AwsBatchQueues / Networking.

For illustrations of some networking scenarios, see the following architecture diagrams.

Topics