VPC Endpoint Support

[aws-samples]

VPC Endpoint Support

[sean-smith]

@Shattoww Currently imagebuilder uses the default VPC. My guess is this is the issue since it's not using the one you've configured with the IGW. We've got a patch to change this in #55 however this is contingent on pcluster 3.1.3 getting released with aws/aws-parallelcluster#3874. Should be ~2 weeks until we can support selecting the VPC.

From that PR is:

Of note, the subnet passed in as a parameter should have internet access (i.e private subnet with NAT gateway routes, or a public subnet). When a public subnet is used, it must have MapPublicIpOnLaunch enabled as image builder won't automatically map a public IP address and the image build will timeout.

My question is if it's a private subnet with an IGW how does it reach the internet?

[Shattoww]

Indeed that was it - we re-created the default vpc to allow egress and the stack launched fine. Side note, we shuffle most of our egress traffic through some network appliances hosted in a different account for the NAT part of the equation, not that it matters. Thanks for the tip and that feature will be great as we near production.