1

I would like to migrate from AWS ELB to API Gateway with an AWS EKS Cluster. Reasons: Cost savings, the number of requests is not too large, lower latency, caching, and other things. One problem: I will need to keep both running for while.

That's the scenario:

enter image description here

I tried to use a private NLB with a VPC Link to access EKS Services that's ok, however, AFAIK I would need one NLB per service, and I have more or less 15 services, which would increase the cost a lot. So, I would like to have a suggestion to connect the API gateway to EKS services, that's cost-effective and have a better performance than ELB, I heard things like use another ingress as an entry point but not sure if that's possible.

Ricardo Cunha
  • 2,013
  • 6
  • 24
  • 42

1 Answers1

0

You should opt for this

User -> API Gateway -> Private Link -> VPC Endpoint

Inside VPC, EKS could be configured with Horizontal Node scaler(handle scaling of the system), or Karpenter (karpenter.sh)

Richard Rublev
  • 7,718
  • 16
  • 77
  • 121