简体   繁体   English

通过 EKS 从 AWS ELB 迁移到 API 网关

[英]Migration from AWS ELB to API Gateway over EKS

I would like to migrate from AWS ELB to API Gateway with an AWS EKS Cluster.我想使用 AWS EKS 集群从 AWS ELB 迁移到 API Gateway。 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:那是场景:

在此处输入图像描述

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.我尝试使用带有 VPC 链接的私有 NLB 来访问 EKS 服务,这没问题,但是,据我所知,每个服务我需要一个 NLB,而且我有或多或少 15 个服务,这会大大增加成本。 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.所以,我想有一个建议,将API网关连接到EKS服务,这比ELB具有成本效益和性能,我听说过使用另一个ingress作为入口点,但不确定是否可行。

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 )在 VPC 内部,EKS 可以配置水平节点缩放器(处理系统缩放)或 Karpenter ( karpenter.sh )

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM