Skip to content
Tutorials Center
My learning

Topics

Lesson 2 of 70 ยท Getting started with AWS

Creating and Securing an Account

Open an AWS account, lock down the root user with MFA, create an admin identity, set budget alerts, understand the free tier and credits, and see why AWS Organizations matters.

An AWS account is the basic container for everything you build: resources, permissions and the bill all belong to one account. Opening one takes about ten minutes, but what you do in the first hour decides whether the account stays safe and cheap. Stolen root credentials and surprise bills are the two classic beginner disasters, and both are easy to prevent.

You do not need an account to follow this tutorial, because every runnable example is a stand-in. This lesson is still worth reading: it is the checklist you would follow before trying any real command, and the concepts (root user, MFA, budgets, Organizations) come back in later chapters. All console steps here are read-only descriptions. The two runnable examples are Python models of a budget alarm and of an account-hardening checklist.

What you need to sign up

The sign-up flow asks for an email address, an account name, a password, a phone number for verification, and a payment card. The card is required even when you only plan to use free services; AWS uses it to bill anything beyond the free allowance. The email address you give becomes the root user, the identity that created the account.

The steps, in console terms:

  1. Go to the AWS sign-up page and choose to create an account.
  2. Enter the root email address and an account name, then verify the email with the code you receive.
  3. Choose a strong, unique root password.
  4. Enter contact details, accept the customer agreement and add the payment method.
  5. Verify the phone number, then choose a support plan (Basic support is free).
  6. Sign in as the root user.

Use an email address that belongs to your organization or to you for the long term, ideally a shared mailbox rather than one person's inbox when it is a company account, because AWS sends security and billing notices to it and password recovery depends on it.

The root user is special

The root user has unrestricted access to every resource and to the billing settings. IAM policies cannot limit it (only organization-level guardrails can, which you will meet at the end of this lesson). That power is exactly why you should barely use it. The rules most teams follow:

  • Turn on multi-factor authentication (MFA) for the root user immediately.
  • Never create access keys for the root user. If an access key for root leaks, the whole account is lost.
  • Use the root user only for the small set of tasks that require it, such as changing the account's name or root email, closing the account, changing the support plan, and restoring access when IAM is broken.
  • Do all daily work as another identity: an IAM Identity Center user or an IAM role, covered in IAM Users, Groups and Roles.

MFA adds a second proof to the password. AWS accepts passkeys and security keys (FIDO2) and authenticator apps that generate six-digit codes. A hardware or passkey device is the strongest choice, because it cannot be phished by a fake sign-in page the way a typed code can. Register a second MFA device for the root user as a backup, so losing a phone does not lock you out.

flowchart LR
    R["Root user<br/>MFA, no access keys"] -->|"creates once"| A["Admin identity<br/>Identity Center or IAM role"]
    A --> D["Daily work<br/>build and deploy"]
    R -.->|"rare tasks only"| T["Close account<br/>change support plan"]

Use the root user once to set up an admin identity, then keep it in a safe place for rare tasks.

Billing alerts first, resources second

Cloud costs are variable, so you want a warning before the bill arrives. In the Billing and Cost Management console you create a budget: an amount (for example 20 USD per month) with alert thresholds. A typical setup sends an email when the actual spend passes 50 percent, 80 percent and 100 percent of the budget, and when the forecasted spend is expected to exceed the budget. The forecast alert is the early warning that matters most, because it fires while you can still turn something off.

A few more habits help:

  • Enable access for IAM users and roles to billing information, so a non-root admin can see costs (this is a root-only switch in the account settings).
  • Turn on free tier usage alerts if your account type offers them.
  • Check the Cost Explorer page weekly while you are learning. Cost Management and Optimization goes much deeper.

The model below imitates a budget with threshold and forecast alerts. It is not AWS Budgets, but it uses the same idea: compare the actual spend so far, and a straight-line projection of the month, against the limit.

Python A budget with actual and forecast alerts

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Run it and notice on which day the forecast alert fires compared with the first actual-spend alert. The forecast fires earlier, which is why you should always configure one.

The free tier and credits

AWS has offered several kinds of free usage over the years, and the rules change. As of this writing, newly created accounts can start on a free plan that comes with a sign-up credit and the chance to earn more credits by trying services, and that stops charging when the credits or the plan period run out unless you upgrade to a paid plan. Older accounts may still follow the previous model: a limited allowance of some services for 12 months, plus a handful of services that are always free up to a limit. Check the Billing console for the exact terms that apply to your account, because they are the only authoritative source.

Whatever your plan is, remember three things:

  • Free allowances are per service and per unit. A free small server does not cover the storage, the public IP address or the data transfer that comes with it.
  • Some resources keep billing even when they look idle: a stopped server's disk, an unattached public IP address, a NAT gateway, a load balancer.
  • The safest learning workflow is create, experiment, delete. Tags and a budget help you remember what to remove.

AWS Organizations: a preview

When you have more than one account (a common and good practice: one for production, one for testing, one for shared tooling), AWS Organizations groups them under a single management account. It provides consolidated billing, lets you place accounts in organizational units and apply service control policies (SCPs) that set the outer limit of what any identity in those accounts can do, even the root user of a member account. You can ignore Organizations while you are learning with a single account. Multi-Account Strategy and Control Tower returns to it.

A hardening checklist

Put the points of this lesson together and you get a short checklist. The stand-in below scores an account's state against it. The checks are real recommendations; the score is just a teaching device.

Python Score your account against the checklist

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which is the best practice for the root user's access keys?

    Root access keys give unrestricted access to the account and cannot be limited by IAM policies, so the recommendation is to never create them.
  2. 2. Why is a forecast alert on a budget more useful than only a 100 percent actual-spend alert?

    A forecast projects the month from the spending so far, so it fires earlier than the actual-spend threshold. Standard budget alerts only notify you; they do not stop resources.
  3. 3. Which task genuinely needs the root user?

    A small set of account-level actions, such as closing the account or changing the root email, require the root user. Daily tasks should use a non-root identity.
  4. 4. What can AWS Organizations add that a single account cannot?

    Organizations manages many accounts together: consolidated billing, organizational units and SCPs that limit what member accounts can do.

Summary

  • An AWS account holds your resources, permissions and bill; the sign-up identity is the root user.
  • Protect the root user with MFA, give it no access keys and use it only for rare account-level tasks.
  • Create a budget with actual and forecast alerts before you build anything.
  • Free tier rules change and cover specific services and units; check the Billing console and delete experiments when done.
  • AWS Organizations groups multiple accounts for billing and guardrails such as SCPs.

Next: Console, CLI and SDKs.