<p>I have a EKS cluster which servers publicly available end points. However, i want to now add an end point which should only be accessible in the same VPC. How can i achieve something like this in EKS. For example, let a service A only be accessible from within the same VPC.</p>
<p>is this possible to natively achieve in EKS (Kubernetes) where I can place the Lambda in the same VPC as EKS cluster and then only allow communication between the two. I dont want the end point to be available publicly. I don't think i can use ClusterIP service as it only lets resources inside the cluster communicate. can I use a different service type to let service be accessible in only a VPC.</p>
<p>Any help here would be really great, Thanks.</p>

opensource-developer
<p>If you already have an AWSLBController, deploy an ingress with <a href="https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.4/guide/ingress/annotations/#scheme" rel="nofollow noreferrer">internal</a> load balancer annotations.</p>
<p>Then your lambda in the same VPC may reach this load balancer.</p>
<p>Additionally, I would choose to set up a <a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zones-private.html" rel="nofollow noreferrer">private hosted zone</a> in Route53 as opposed to setting up a DNS record with a load balancer's CNAME value.
Because load balancer DNS name is difficult to memorize,</p>
