Home/Services/AWS cloud

AWS cloud

Production hosting, not a diagram: a load balancer that spreads traffic, a database you can restore, and heavy work moved off the page your customers are waiting on.

I have kept live systems on AWS at 99.9% availability: EC2 behind an application load balancer, auto-scaling, and RDS that is not a single instance you are afraid to touch.

The usual shape is a web tier that stays small, Lambda or workers for anything slow, and Kinesis when events have to move as they happen. Telemetry, orders, status changes. Not a cron that hopes last night finished.

I do not migrate everything in a weekend. We pick the risk that would take the product down, move that, and leave a rollback.

What this includes

  • •EC2 servers with auto-scaling and a load balancer, set up to stay online when traffic jumps.
  • •RDS (managed MySQL or PostgreSQL) with backups, plus read copies where reports need them.
  • •Lambda functions and queues for work that should finish after the customer has moved on.
  • •Kinesis streaming when events have to move in near real time instead of waiting for a nightly batch.
  • •Private networking, firewall rules, and secret storage, so your database is never open to the internet.

What you leave with

  • •A deploy path that does not require SSH into one box.
  • •A database you can restore, and a read path that does not melt the primary.
  • •Background jobs that keep running when the web tier restarts.

How it starts

I look at what is already deployed, what breaks when traffic jumps, and what is still on a single machine. Then we move one risk at a time.

When to use it

Use this when the app runs on one server and now has to survive real traffic, or when AWS is already set up and nobody owns it.

Send a brief
Engagement

Ways to work together

01

Join your team

A senior engineer inside your team. I work in your codebase, standups and code reviews, and stay long enough to own a real part of the product. Under the hood: Laravel, Node.js, Python or AWS.

Full-time or long contract
02

Work solely for your company

A dedicated engineer for one company. I take the product from planning to the live version: backend, data, hosting and screens, with your product as my focus.

Dedicated contract
03

One project

A clearly defined build, then a clean handover: an MVP, taking an AI-built prototype (Lovable, Bolt, Cursor) to production, a migration, or an AI feature. Get in touch to discuss scope and pricing.

Fixed-scope project