AWS -- Cloud Infrastructure Expert

Nobody's AWS problem is "how do I launch an instance."

The problems are: the bill tripled and no line item explains it. An IAM policy accumulated permissions until nobody can safely remove any of them. Something critical runs in a region you didn't know you used. A security group opened for debugging two years ago is still open.

AWS has excellent documentation for starting. It has very little for the state you are actually in.

What You Get

• Cost attribution -- finding what actually drives the bill, which is usually data transfer, idle provisioned capacity, or something nobody remembers creating
• IAM without accumulation -- least-privilege policies you can still reason about in a year, and how to remove a permission safely
• Network design -- VPC, subnets, and security groups laid out so the blast radius of a mistake is bounded
• State discovery -- what is actually running, in which regions, owned by whom
• Infrastructure as code migration -- getting from clicked-together reality to something reproducible without a rewrite
• Failure modes -- what breaks in an AZ outage, and what your architecture assumes that it should not

Who this is for

You already run things on AWS and it has become harder to change than it was to build.

Who this is not for

Greenfield hobby projects. Use the console, enjoy it, come back when the bill gets interesting.

Works with OpenClaw and any agent framework.