<p>I am using EKS and I want to enhance the security by keeping one out of the total two nodegroups into a private subnet. However, I have read few documents from AWS where it is a need that if a nodegroup has to be launched in private subnet then there has to be a NAT gateway connection so that the nodegroup can connect with the AWS Control plane VPC and communicate to the master. Putting up NAT will be too much because of its charges. If there is a workaround which I can use then I would be happy to know about it. I know using eksctl we can launch a nodegroup into private subnet without NAT. But I need something which can be done without eksctl. If I am wrong in my understanding then please do let me know.</p>

Kaustubh
<p>AWS provides an explanation and an <strong>VPC template</strong> (<code>amazon-eks-fully-private-vpc.yaml</code>) for EKS without NAT in a post titled:</p>
<ul>
<li><a href="https://aws.amazon.com/premiumsupport/knowledge-center/eks-cluster-node-group-private-network/" rel="nofollow noreferrer">How do I create an Amazon EKS cluster and node groups that don't require access to the internet?</a></li>
</ul>
<p>Instead of NAT, <strong>VPC interface endpoints</strong> are used for:</p>
<ul>
<li>ec2</li>
<li>logs</li>
<li>ecr.api</li>
<li>ecr.dkr</li>
<li>sts</li>
</ul>
