Closed rvencu closed 2 years ago
Well, I changed the logic in the bootstrap script and launched the headnode on the public subnet instead.
This is by design, the reason is you can ssh into the headnode only via Cloud9. of course if this does not work for you feel free to change the config.
Thanks
I noticed the head node was created in the private subnet. Checked the parameters in the cloudformation where I supplied my custom VPC details:
PrivateSubnetAId | subnet-0112272390ac53c95 | - -- | -- | -- PublicSubnetAId | subnet-79775a34 | - PublicSubnetBId | subnet-2fd94770 | - VpcId | vpc-4678d63bAnd the head node was created in the private subnet.
As a consequence, I cannot SSH into the EIP of the head node.
I can see the code makes this deliberately https://github.com/aws-samples/1click-hpc/blob/93d1930b4531d5f437defe106675fa0bfe321fd7/scripts/Cloud9-Bootstrap.sh#L74
If it is supposed to be there, then please explain how to SSH into the head node using the elastic IP.