Expose Services in EKS via AWS API Gateway
This blog gives you a high-level overview of exposing services running inside a private Kubernetes cluster @AWS Public Cloud using EKS managed service to the external world. You will get a taste of Architecting the system given a set of constraints. So, if you want to go beyond “Hello World Kubernetes”, continue reading!!!
A company has some services running in AWS Cloud and some in On-Premise Data Center. The company is looking to close its On-Premise data centre for cost reason and has asked the application team to move all the services to AWS.
The blog does not focus on the actual migration planning. If you are looking for details around it, do take a look at this blog.
Mentioned below are some of the details which needs to be considered to come up with the deployment architecture on AWS —
- The On-Premise services are running in a self-managed Kubernetes Cluster.
- The services to be moved to AWS needs to be scalable as the product has done very well in the market.
- There is a new requirement to impose rate limit on the APIs being served.
- Services already running on AWS is leveraging AWS API Gateway, which has AWS Web Application Firewall (WAF) integrated with it to improve the security posture of the services.
- Some of the team members already have expertise with AWS API Gateway.
- There is a mandate to reduce the operational cost of the…
