Free AWS Review

A second pair of eyes on your cloud setup

Describe what you run today. I'll reply with the few things most worth fixing first, in plain language. No sales pitch, no obligation.

What I look at

Four areas, in order of risk

Access and security

IAM roles and keys, public buckets, secrets in code, and how people sign in.

Infrastructure as code

What is in Terraform, what was clicked together, and how risky a rebuild would be.

Deploys and pipelines

How code gets to production, who can do it, and what happens when it breaks.

Visibility and cost

Whether you would know about an outage before your customers, and where money leaks.

Example

What a Free AWS Review reply looks like

A typical reply for a small startup on AWS, sorted by what to fix first:

Fix this week

Two IAM users have admin rights and access keys older than a year. Move them to roles with MFA and delete the keys.

Fix this month

Your GitHub Actions deploy uses stored AWS keys. Switch to OIDC so each run gets short-lived credentials.

When you have time

Dev servers run all weekend and CloudWatch logs never expire. A schedule and a 30-day retention save roughly 10 percent of the bill.

Tell me about it

Start here

I reply within one business day. Your details are used only to answer you.

What happens next

  1. I read your description.No call needed. The description you send is enough to start.
  2. You get a reply within one business day.The few things most worth fixing first, in plain language.
  3. You decide what to do with it.Fix it yourself, or ask me to do it for a fixed price. No sales pitch, no obligation.

If you want me to fix what I find, typical next steps are the AWS cost review (from $150), a CI/CD pipeline ($300) or the AWS Foundation ($600). How payment works.

Prefer a checklist? Run the S3 security checklist. Want a quick number first? Try the savings estimator or the policy checker.

Free AWS Review: common questions

Is the Free AWS Review really free?

Yes. You get the written findings for free. If you want me to fix them, I quote a fixed price first, and you are free to fix them yourself.

Do I need to give you access to my AWS account?

No. A short description of what you run is enough for the first review. If we work together later, I use a read-only role, never your passwords or keys.

What should I write in the description?

Which services you use (for example EC2, EKS, RDS, S3), how code gets deployed, whether you use Terraform, your rough monthly bill, and what worries you most.

How long does it take?

You get a reply within one business day.