AWS Account Setup — Complete Guide
AWS Account Setup — Complete Guide: free step-by-step lesson with examples, common mistakes, and interview tips — part of AWS Cloud Tutorial on Toolliyo Academy.
On this page
AWS Cloud Tutorial · Lesson 3 of 100
AWS Account Setup
Core services → Projects
Core services · 1 — AWS basics · ~6 min · AWS — Foundations
What is this?
An AWS account is your billing and security boundary. Root user creates the account; day-to-day work uses IAM users or SSO with MFA enabled.
Why should you care?
AwsVerse uses separate accounts for dev, staging, and prod with AWS Organizations for guardrails.
See it live — copy this example
Run in AWS CloudShell / local AWS CLI v2, or follow the matching steps in the AWS Console (Free Tier).
aws organizations create-account \
--email awsverse-dev-admin@example.com \
--account-name "AwsVerse-Dev" \
--role-name OrganizationAccountAccessRoleWhat happened?
- Creates a member account under an organization.
- The management account can assume OrganizationAccountAccessRole into the new account.
Practice next
- Create or sign in to your AWS account with a unique root email.
- Enable MFA on the root user immediately.
- Create an IAM admin group and avoid daily root login.
- Enable AWS Control Tower in a sandbox org if available.
- Tag the account with Environment=lab.
Remember
Root is for break-glass only. MFA on root and admins. Use Organizations for multi-account.
AwsVerse account vending
Each product squad needs an isolated dev account.
Outcome: Organizations plus Control Tower provisions accounts with baseline guardrails.
Interview prep for this lesson
Practice these questions aloud after reading—each links to a full structured answer.
Sign in to ask a question or upvote helpful answers.
No questions yet — be the first to ask!
