Creating an AWS Account Safely
Creating an AWS account takes about fifteen minutes, but the first hour afterwards matters most. This page walks through signing up, locking down the all-powerful root user, creating a safer everyday login and setting up billing alerts before you launch anything.
Step 1: Sign up
- Go to aws.amazon.com and choose to create an account.
- Enter an email address and an account name. Use an email you will keep for years; it becomes the root user's login. A dedicated address such as a new Gmail alias works well.
- Verify the email with the code AWS sends, then set a long, unique password (a password manager helps).
- Enter your contact details and a payment card. AWS uses the card to verify your identity and to bill any charges. Many learners in East Africa use a bank debit card or a virtual card that supports online payments.
- Verify your phone number by SMS or voice call.
- Choose the free Basic support plan. Paid support plans are for businesses.
The Free Tier
AWS offers a Free Tier so new customers can explore without paying, but the details change. In 2025 AWS changed how it works for new accounts: rather than only a list of always-free allowances, new customers receive promotional credits and choose between a free plan and a paid plan during sign-up. The rules on which services are covered, for how long and what happens when credits run out differ between the plans and may change again. Read the official AWS Free Tier page before you start and check your remaining credits in the Billing console.
"Free Tier" never means "everything is free". Some services, larger instance sizes and some features are not covered, and usage above the allowance is billed. Assume anything can cost money until you have checked.
Step 2: Secure the root user
The email and password you signed up with belong to the root user. It can do anything, including closing the account and changing payment details, and IAM permissions cannot restrict it. If someone steals it, they can run up huge bills.
- Sign in as root, open the account menu and choose Security credentials.
- Under Multi-factor authentication (MFA), assign a device: a passkey or security key, or an authenticator app such as Google Authenticator or Microsoft Authenticator. AWS now requires MFA on root users, but set it up yourself immediately rather than waiting for a prompt.
- Make sure the root user has no access keys. If any exist, delete them.
- Store the password and MFA recovery details somewhere safe.
After this, use the root user only for the few tasks that need it, such as changing the account's payment settings or closing the account.
Step 3: Create an everyday admin login
AWS recommends IAM Identity Center for people who sign in to AWS. It gives you a personal user with a sign-in portal and short-lived credentials.
- In the console search bar, open IAM Identity Center and choose Enable. If asked, enable it with AWS Organizations (this is free and simply creates an organisation with your account as its management account).
- Under Users, add a user for yourself with your name and email, and accept the invitation email to set a password and MFA.
- Under Permission sets, create one from the predefined AdministratorAccess policy. (Later, use narrower permission sets.)
- Under AWS accounts, select your account and assign your user with that permission set.
- Note the AWS access portal URL shown on the Identity Center dashboard and bookmark it. From now on, sign in there, not as root.
Some older tutorials create an IAM user with a password instead. That still works, but Identity Center is the recommended approach for humans because it avoids long-lived passwords and access keys tied to IAM users. The IAM page explains the difference.
Step 4: Set up budgets and alerts (before anything else)
Do this before launching your first server. In the console open Billing and Cost Management, then Budgets:
- Choose Create budget and use the Zero spend budget template. It emails you as soon as your spending goes above zero, which is ideal while you learn.
- Create a second Monthly cost budget with a small amount you can afford, with email alerts at, for example, 50%, 80% and 100% of it, including forecasted spend.
- In Billing preferences, turn on Free Tier usage alerts and add your email.
- Check that the alert emails are not going to spam.
Budgets warn you; they do not switch anything off by default. You still have to act on the email. See Pricing, Billing & Cost Management for more.
Step 5: Practise safe habits
- Pick one Region for practice and stick to it, so you always know where your resources are.
- Clean up after every session: terminate instances, delete load balancers, NAT gateways, databases and unused Elastic IP addresses. Stopping an EC2 instance halts compute charges but its disk still costs money.
- Never commit access keys to GitHub or paste them in chats. Bots scan public repositories for keys within minutes.
- Check the Bills page weekly while you are learning.
If you ever see charges you do not recognise, or think a key has leaked, act at once: delete the key, check for unknown resources in every Region and contact AWS Support from the console. AWS has helped many learners who acted quickly.
Key points
- Sign up with a long-lived email, a strong password and the free Basic support plan.
- Protect the root user with MFA, give it no access keys and stop using it for daily work.
- Use IAM Identity Center for your everyday admin login.
- Create a zero spend budget and a monthly cost budget before you launch anything, and clean up after practising.
- Free Tier rules changed in 2025 and can change again; always check the official Free Tier page.
Tip: use the ← and → keys to move between pages.
