What are your API Gateway horror stories?

0
14
Asked By TechyTurtle99 On

Hey everyone, I've come across some alarming information about API Gateways. It seems that if an endpoint gets discovered by a rogue bot, it could really drain your funds quickly. I'm curious if anyone can explain this in more detail and share any personal experiences they've had with API Gateway issues. Thanks!

3 Answers

Answered By CodeNinja42 On

Yeah, that's definitely a real concern! If your API Gateway endpoint is public without proper authentication or request limits, bots can hammer it with requests and run up a massive bill in no time. I've seen it happen when someone accidentally left a test Lambda function exposed and forgot to set any rate limits—the costs ended up in the hundreds overnight! Always make sure to use IAM auth, Cognito, or custom tokens, and implement throttling at the gateway level. Cloud providers might let you burn through credits if you forget all that.

Answered By DevDynamo23 On

One basic tip is to always disable the default endpoint and add rate limiting. A Web Application Firewall (WAF) can help, too, but keep in mind that it’s typically priced per request as well, so it could get costly if not managed properly!

Answered By GuruGadget77 On

Exactly! It's all about securing your endpoints. Using usage plans, API keys, and rate limiting can help prevent these kinds of issues. There are definitely horror stories out there, but most can be avoided with the right precautions. Just remember that improper setup can lead to chaos!

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.