Day 6: Connecting the dots 🔗
It is the final day of 2025, and while many are closing their laptops, I decided to push one last update for my #100DaysOfCloud challenge.
Yesterday (Day 5), I created a Python function on AWS Lambda. It worked, but only I could run it from the AWS Console. A backend that nobody can talk to is useless.
Today, I introduced Amazon API Gateway.
What I did
I didn't write more code. I focused on Architecture.
I navigated to my existing Lambda function.
I added a Trigger.
I selected API Gateway -> Create a new API -> HTTP API (Open).
The Result
In less than 2 minutes, AWS gave me a public URL (https://...amazonaws.com). When I paste that URL into my browser (or send a request from Postman), the Gateway routes the traffic to my Lambda, executes the Python code, and sends back the response.
Why this matters?
I have officially built my first Microservice. This architecture (API Gateway + Lambda) is the standard for modern serverless applications. It decouples the "Door" (Gateway) from the "Logic" (Lambda), allowing me to handle traffic spikes without crashing a server.
The foundation is set. 2026, I'm ready for you. 🚀
Happy New Year!
Top comments (0)