1.9 Your first account and your first deploy

What this is and why it exists

This is the topic where the course stops being reading and becomes an account with your name on it. Account signup is a console workflow — there is no command line for it and no provider-neutral path — so this lesson teaches the decisions and hazards, and the provider's own getting-started guide under Go deeper carries the clicks. Read this WHOLE lesson before starting the signup: the order of operations is the protection.

The vocabulary

• Root (or owner) account — the identity created at signup that can do anything, including delete everything and change billing.
• MFA (multi-factor authentication) — a second proof of identity beyond the password, usually an authenticator app.
• Free tier — the set of services a provider lets you use without charge, within limits, for learning.
• Billing alert — an automatic notification when spending crosses a threshold you set.
• Static site — a site of plain files — HTML, CSS, images — needing no server-side code; the classic first deploy.

The mental model

The order of operations IS the safety. Lock the master key first, set the smoke alarm second, and only then bring anything into the house:

First, the root login gets MFA in the first minutes of the account existing, before anything is deployed — a hijacked cloud account mines cryptocurrency on your card within hours. The root identity is then put away: create a separate everyday working identity, and keep root for the rare acts only root can do.

Second, the billing alert goes on BEFORE the first deploy, not after the first surprise. Set a threshold near zero — a few hundred rupees — so the first paid rupee is a notification, not a month-end discovery.

Third, know the free tier's shape before trusting it: parts are always-free within limits, parts expire after months, and a resource left running quietly crosses from one to the other. The habit that protects you is a weekly look at the billing page — it is the one page that never lies about what is really running.

Then the region: pick an Indian region for your first deploys — closest to you, and the residency questions do not arise for your own learning data.

Last comes the deploy itself: put a static site — even one page with your name — into the provider's static hosting, and open it from your phone over mobile data. That last step is the point: something you made, reachable from any network on earth.

What you should now be able to explain or do

Explain why MFA-on-root precedes everything and why the billing alert precedes the first deploy. Describe the free tier's two kinds of "free" and the trap between them. State what a static site is and why it is the classic first deploy. (The doing half — the signup clicks — belongs to the provider's guide under Go deeper; the explaining half above is what this lesson holds you to.)

Check yourself