I Built an AWS Lambda Function Without an AWS Account
Olajobi Haneef2 min read·Just now--
My AWS account was inactive due to a billing issue, but the clock was ticking. I had a task for my internship at Algoritic Inc., a fintech startup, to build a Lambda function for their product, Monietar. I couldn’t wait for support tickets or billing cycles, so I turned to LocalStack.
The Mission
The task was straightforward but critical. I needed to build a Lambda function in TypeScript that accepts a JSON transaction payload, validates the data, and logs it to CloudWatch. Everything had to be deployed using AWS SAM, documented so well that anyone could clone the repo and have it running in minutes.
What is LocalStack?
LocalStack is essentially AWS running inside a Docker container on your machine. It emulates services like Lambda, CloudWatch, and IAM at zero cost. You use the same commands and expect the same behavior, all without needing an active AWS account or an internet connection.
How I Built It
The core is a TypeScript handler that receives the transaction and checks for required fields. Once validated, it logs the payload to CloudWatch with precise timestamps and returns a clean response. The AWS SAM template defines the Lambda, the IAM roles, and the log groups, while a simple Docker Compose file spins up the entire LocalStack environment with one command.
What CloudWatch Captures
Even though it’s local, the logging is real. CloudWatch captures exactly when the Lambda starts, the full incoming transaction data, and the final success or error status. You get structured logs that look and feel like the actual AWS console, making debugging seamless.
The Takeaway
You don’t need a live AWS account to build production-ready infrastructure. LocalStack is how you stay sharp and keep shipping when a cloud bill or a locked account stands in your way. This is exactly how I’ve been building lately, and the workflow is rock solid.
Check out the full repo here: monietar-lambda-poc GitHub: haneeo3
