Move your company to the cloud the easy way.
Set up by hand, a cloud account becomes a thing nobody wrote down, nobody can explain, and only one person can safely touch. Here is the decision that prevents all of it.
Somebody set up the cloud account. It works. It has worked for two years. And nobody can tell you what is in it, what each piece is for, or what would break if you turned one off. The person who built it left in March. Their replacement is scared to touch anything, so nothing gets touched, and the bill goes up every month for reasons nobody can name.
That is not carelessness. It is one small decision, made in the first week of a project, usually by nobody.
the problem
Clicking is not a plan.
It is a thing you did once, that nobody watched, and nobody can repeat.
Setting up a cloud account by hand feels productive. You work through the screens, you answer the questions, and at the end there is a real running server. It worked. You are done.
But look at what you actually made. A running server, and nothing else. No list of what you clicked. No note about why. The only copy of that process is in one person’s memory, and memories are not backups.
A dashboard is a place to do things. It is not a place to describe them.
That difference sounds small, but here is what it costs you.
You cannot change it safely. The only way to find out what a click does is to click it. Every change is a live experiment on the thing your customers are using, because there is nowhere else to try it.
You cannot hand it off. All of it lives in one person’s head, and the account is often not even yours. It belongs to the people who built it, with other clients sitting in it, so there is no login to hand over at all. What gets handed over is a guess.
You cannot find what to turn off. One click quietly makes several things, and some of them charge by the hour whether anyone uses them or not. You delete the piece you remember. The rest keeps billing, and nobody notices, because the bill arrives as one number.
The usual fix works once. Then it rots.
Every team tries the runbook first. Forty steps, with screenshots. It helps for a quarter, then the cloud provider moves a button, step twelve is wrong, and nobody finds out until somebody follows it at two in the morning.
So the smarter version is the script: the clicks written out as commands. It is text, a computer runs it, and it is genuinely better. But it is still a list of steps, and a list of steps only works on an empty account.
# setup-prod.sh "just run this to rebuild everything" aws ec2 create-vpc --cidr-block 10.0.0.0/16 aws ec2 create-subnet --vpc-id vpc-???? # paste the id printed above aws rds create-db-instance --db-instance-identifier prod-db ... # run it twice: fails, all of it already exists # run it and it errors: half an environment, and no list of which half
Run it on the account you have actually had for two years and it falls over on line two, because that network already exists. It cannot skip what is done or fix what is wrong. It only ever describes starting over, and you are never starting over.
The owner feels this as a calendar problem. Every change waits on one person, and the bill only goes up, with no way to break the number down.
The engineer feels it as fear. Nothing can be deleted, because nothing can be proven unused. So the pile only grows.
There is a better question than what did you click?
It is: what should be true?
how good teams run a cloud
Write it down. Let a robot do it.
The whole idea is one move.
Instead of going into the dashboard and doing things, you write a file that says what you want to exist. Two servers, this size. One database, this big, copied every night.
Then a program reads your file, looks at what is actually in your account, and closes the difference. That is the entire idea, and everything good about it comes from one small change: you stopped doing, and started describing.
A dashboard gives you a photo of the kitchen. A file gives you the recipe.
You can stare at a picture of a cake all day and still not be able to make one. A recipe is worth more, precisely because you can hand it to somebody else.
The tool most teams use is called Terraform, and the file is not code in the scary sense. It is a list of things and their settings.
One rule makes all of it work, and it is not a technical one: once the file describes something, nobody changes that thing by hand. The dashboard becomes a place you look, not a place you touch.
Here is what happens every time you change something.
The file
You write what should be true, not the steps to go and make it true.
The preview
It compares your file to what is really out there and lists the difference. Nothing has happened yet.
The reviewer
A person reads that list before any of it is real. This is the step a dashboard does not have.
The robot
It makes the cloud match the file. Adds, changes, and removes, in an order that works.
The ledger
One list of everything it built, so it can find all of it again, including the parts you forgot.
The knowledge lives in writing, not in one person’s head.
Which means it survives a vacation, a resignation, and a handoff to a team on another continent. Somebody can read the folder and know what you have, and the same file builds all of it again, in a test copy or in an account you actually own.
now track three scenarios
See it happen.
Pick something that has happened to you, then step through it.
What is going on?
Sales are up and the app has to keep up. Watch how many steps happen before anything is real.
Press See what happens to start.
logs