CODEWITHSUNDEEP
kubernetesamazon-eksamazon-vpckubernetes-nodeport
opensource-developer
opensource-developer

Reputation: 3038

Kubernetes(EKS) and AWS Lambda communicate with each other

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.

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.

Any help here would be really great, Thanks.

Upvotes: 0

Views: 921

Answers (1)

Mehmet Güngören
Mehmet Güngören

Reputation: 2774

If you already have an AWSLBController, deploy an ingress with internal load balancer annotations.

Then your lambda in the same VPC may reach this load balancer.

Additionally, I would choose to set up a private hosted zone 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,

Upvotes: 1

Related Questions