I will build or fix your AWS serverless backend
AWS and AI Agent Engineer
About this Gig
Your AWS backend works. Now make it right before traffic doubles, a Lambda times out, or one deploy breaks something else.
Serverless done properly: small services, clear boundaries, tests, and infrastructure as code, so the backend grows without surprises.
What you get:
- Lambda functions in TypeScript or Java behind API Gateway
- ECS Fargate for long or heavy jobs that don't fit in Lambda
- DynamoDB, PostgreSQL or Aurora Serverless, with a data model built for your access patterns
- OAuth 2.0 / JWT auth where needed
- Queues and events (SQS, SNS, EventBridge) for work that shouldn't block the API
- Tests, CI/CD and Terraform or SAM, so every change deploys the same way
Done by a team lead with 10 years of experience on serverless AWS platforms for enterprise, including moving one off a monolith, service by service.
Built AI-driven: Claude Code from spec to review, with tests on every change.
How it works:
1. Share the repo or the idea, and what has to work
2. A short plan first, so you see the scope before any code
3. Small steps, with progress every few days
Not sure it fits? Send a message before ordering.
Cloud Provider:
Amazon Web Services
Expertise:
Deployment
•
Migration
•
Debugging
•
Development
•
Performance
Frameworks:
Npm
•
Terraform
•
Other
FAQ
TypeScript, Java or Kotlin?
Any of them: TypeScript (Node.js, NestJS), Java (Spring) or Kotlin, on Lambda or ECS Fargate.
What access is needed?
For a review: the repo with its infrastructure code, or read-only AWS access. For building: a dev account or a role with limited rights. No production keys.
Terraform, SAM or CloudFormation?
Whatever you already use. New projects start with Terraform or AWS SAM
Will it run in our AWS account?
Yes. Everything is deployed as code, so it's easy to review and easy to remove.
Is the code written by AI?
Partly, on purpose. Claude Code writes the first draft from a short written plan. Every change is then reviewed by hand and covered by tests before delivery. That keeps the work fast and the code easy for your team to maintain.
Lambda or containers?
Lambda first. A job that runs longer than Lambda's 15-minute limit, or needs more memory, moves to ECS Fargate.
DynamoDB or PostgreSQL?
Whichever fits your data. DynamoDB when access patterns are known and traffic is high. PostgreSQL or Aurora Serverless when you need joins, reports or flexible queries. Already have one? It stays.

