Aws-parallelcluster: VPC setup when use_public_ips is set to false

Created on 1 Apr 2019  路  2Comments  路  Source: aws/aws-parallelcluster

Environment:

  • AWS ParallelCluster: 2.2.1
  • OS: ubuntu1604
  • Scheduler: slurm
  • Master instance type: t2.medium
  • Compute instance type: t2.medium

Bug description and how to reproduce:
Are there any examples on VPC setup when use_public_ips is set to false? When I set use_public_ips=false along with default vpc, cluster formation is stuck at AWS::AutoScaling::AutoScalingGroup | ComputeFleet.

We are spinning up multiple clusters and running out of elastic IP limits. I don't need compute instances to have public IPs. Network configuration documentation says

_With use_public_ips set to false The VPC must be correctly setup to use the Proxy for all traffic. Web access is required for both Master and Compute instances._

Appreciate any pointers!

Thanks
Santi

closing-soon-if-no-response help wanted

Most helpful comment

Hi @adavanisanti,

This is rather confusing and we'll update the docs to make it clearer. To make this work, you'll need a public and private subnet, the private subnet requires a NAT gateway. To create these subnets do:

  1. In the VPC Dashboard , click "VPC Wizard"

image

  1. Select the second tab "VPC with Public and Private Subnets"

image

  1. Create the VPC, giving it a name, like public-private:

image

  1. Enable "Auto-assign public ip's" on the Public Subnet.

image

  1. From your ~/.parallelcluster/config file add a vpc section that includes your newly created vpc and subnets, and reference it in your cluster section:
[cluster mycluster]
...
vpc_settings = public-private

[vpc public-private]
vpc_id = [VPC you created]
master_subnet_id = [Public Subnet]
compute_subnet_id = [Private Subnet]
use_public_ips = false
  1. Create the cluster! When you ssh in, you'll need to grab the public ip from the EC2 console, rather than pcluster ssh cluster.

All 2 comments

Hi @adavanisanti,

This is rather confusing and we'll update the docs to make it clearer. To make this work, you'll need a public and private subnet, the private subnet requires a NAT gateway. To create these subnets do:

  1. In the VPC Dashboard , click "VPC Wizard"

image

  1. Select the second tab "VPC with Public and Private Subnets"

image

  1. Create the VPC, giving it a name, like public-private:

image

  1. Enable "Auto-assign public ip's" on the Public Subnet.

image

  1. From your ~/.parallelcluster/config file add a vpc section that includes your newly created vpc and subnets, and reference it in your cluster section:
[cluster mycluster]
...
vpc_settings = public-private

[vpc public-private]
vpc_id = [VPC you created]
master_subnet_id = [Public Subnet]
compute_subnet_id = [Private Subnet]
use_public_ips = false
  1. Create the cluster! When you ssh in, you'll need to grab the public ip from the EC2 console, rather than pcluster ssh cluster.

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

sumedhjain picture sumedhjain  路  4Comments

afernandezody picture afernandezody  路  4Comments

denysthegitmenace picture denysthegitmenace  路  3Comments

huffmabc picture huffmabc  路  3Comments

anders-lgi picture anders-lgi  路  3Comments