May 11 · 6 min read · You're debugging a Lambda function at 2 AM. The error logs are clean. The CloudWatch metrics are green. But your Lambda is doing something inexplicable — outputting strings that look like configuration options that don't exist in any AWS documentatio...
Join discussion
May 11 · 5 min read · 3 AM. You're on call. Your AWS Lambda monitoring dashboard just sent you a Slack alert that's already 47 reactions deep with skull emojis. The error log shows something your brain refuses to process: your content moderation pipeline just scheduled an...
Join discussion
May 10 · 4 min read · Three AM. You're staring at a CloudWatch log showing your Lambda function firing every 30 seconds when you explicitly set it to run once per hour. You've triple-checked the Terraform. The AWS Console matches your intent. The AI assistant confirmed it...
Join discussion
Apr 24 · 12 min read · TL;DR Built a multi-agent Vacation Planner app using CrewAI (Travel Research Agent + Summarizer Agent) Deployed it to production via Amazon Bedrock AgentCore Runtime using a containerised ECR image
Join discussion
Apr 8 · 8 min read · Every Lambda test starts the same way: you need an event object — and crafting one is annoying. API Gateway v2 events have 30+ fields, SQS needs message IDs, receipt handles, and ARNs, and DynamoDB St
AArchit and 2 more commented
Apr 7 · 5 min read · In the previous article, we exposed our backend using AWS Lambda and Amazon API Gateway, creating a fully functional serverless API. However, real-world applications require more than just an API. To
Join discussion
