HTTP 429 When Calling the Gemini API on AWS

Running into HTTP 429 calling the Gemini API on AWS — and how our team fixed it. 429 is Google’s polite way of saying “slow down.” While building our capstone project (a RAG chatbot running on EC2 that calls the Gemini API), we hit an error that anyone who’s integrated a third-party API has probably run into at least once: HTTP 429 – Too Many Requests. At first we were pretty confused, because everything ran fine locally — no signs of trouble at all. But the moment we deployed to EC2 and tested with multiple concurrent users, requests piled up and Gemini politely declined with a 429.