I'm considering the use of AWS API Gateway for our project, but we're not utilizing Lambda at all. Our setup is based on ECS Fargate, and we have everything behind an Application Load Balancer (ALB). We're particularly interested in features like rate limiting per API key, usage plans, and request validation. Although API Gateway seems like the obvious choice, most tutorials focus on Lambda, and the pricing at 300 million requests per month seems quite steep. Has anyone here successfully implemented API Gateway with container backends, or is it primarily intended for serverless architectures?
3 Answers
Using API Gateway with a VPC Link is quite a popular approach, especially if you're dealing with containerized backends. It allows you to hook up your ALB seamlessly while benefiting from the features API Gateway provides. Just a heads-up, if you're looking to optimize performance, consider that an NLB might be a better fit for routing, as it handles requests at the network level without delving into application data.
Also, remember to consider your latency; using an NLB can be more effective than an ALB in this context.
Just keep in mind that API Gateway can't connect directly to ECS Fargate, so you'll need an ALB or NLB in the mix. That makes the setup a bit convoluted if you’re just going for simplicity. If rate limits from the WAF don’t cut it for you, consider using an API management tool like Kong or APISIX in ECS. They might give you more flexibility and control over traffic routing between your services.
Great point! It can indeed feel hackish at times, but that documentation on interconnecting ECS services really helps to clear things up.
API Gateway can definitely work with container backends, but you'll want to analyze the costs carefully to ensure it aligns with your budget. It's a solid option if you're looking for the advanced features it offers and you have the resources available. Just be mindful, as the costs can add up quickly, especially with high request volumes. If you have engineering support on hand, it might be worth it!
Exactly, it ultimately comes down to your specific needs and budget. If you can manage the costs and you need those added features, go for it!
Totally agree—VPC Link is the way to go for this. I've successfully managed a robust environment using this setup with over 80 services. It definitely handles the traffic well!