I spent my first year as a cloud associate learning things the slow way, mostly by causing small problems and cleaning them up. None of it was in a certification. Here is the list I would hand my past self, the stuff that actually mattered once I was responsible for real infrastructure instead of a lab account.
1. The bill is a map of your architecture
I used to think the cloud bill was finance's problem. It is not. The bill is the most honest diagram of your system you will ever get. If a line item is big and you cannot explain it, you do not fully understand your own architecture. Reading the bill taught me more about how our system actually worked, where the data flowed, what ran when, than any diagram someone drew. Learn to read it early.
2. Tag things on day one, not "later"
Every account I have seen swore it would add tags "once things settle down." Things never settle down. Untagged resources become unattributable cost and unownable risk, and retrofitting tags across a live account is miserable. Tag from the first resource: owner, environment, team. It costs nothing at creation and saves enormous pain later. This is the single cheapest habit with the biggest long-term payoff.
