Welcome to AWS networking: the big picture and a safe personal account
What you will learn
By the end of this module you can explain what a cloud network is, pick a Region and Availability Zones, plan a VPC address range, drive AWS from the command line, and run three small guided labs on your own account without a surprise bill. This is the first of three AWS networking modules. The next two cover VPC design (public and private subnets, route tables, internet gateway) and security groups and network ACLs.
Prerequisites: you know what an IP address, a subnet mask and a default gateway are (the IPv4 chapters of the CCNA path are enough). You do not need any cloud experience.
The analogy: a gated housing society
Think of AWS as a very large city. A Region is a city (Mumbai). An Availability Zone is one separate locality inside that city, with its own power and cooling. A VPC is your own gated housing society: you decide the lane numbers (the IP range), which lanes are open to visitors (public subnets), which are private, who stands at the gate (security groups) and what the main road is called (the route table). The city runs the roads, the electricity and the buildings. You run everything inside your gate.
Everything you create is an API call, and everything lives in one Region, inside a VPC, inside a subnet.
Prefer no hassle? You can practise these exact steps with no AWS account and no bill using the hands-on labs at aws.nwkings.com. Or use your own account: set a budget alert first and delete everything when you finish.
Setting up a personal account safely
Nothing in this module needs a paid service, but a careless account can still cost money. Follow these rules before you create a single VPC.
- Know the current free rules. From the AWS Free Tier pages: accounts created after the July 2025 change get a Free plan. You receive USD 100 in credits at sign-up and can earn up to USD 100 more by completing activities (for example trying EC2). The Free plan ends after 6 months or when the credits run out, whichever comes first. It is limited to eligible services (VPC and EC2 are on the list) and does not charge you during the free period. When it ends you must upgrade to the Paid plan within 90 days, or AWS closes the account and deletes its content. Credits expire 12 months after you open the account. Older accounts may still be on the previous 12-month Free Tier; check your own Billing console.
- Create a budget and alert first. In the Billing and Cost Management console open Budgets, create a monthly cost budget (for example USD 5) and give your email. Chapter 6 walks through it.
- Never use the root user for daily work. The root user is the email you signed up with. Turn on MFA for it (AWS now enforces MFA for root users), store the password safely and then stop using it.
- Use IAM Identity Center, or an IAM user with MFA. Identity Center gives you short-lived credentials through
aws sso login. If you choose an IAM user, enable MFA and avoid long-lived access keys. - Choose a Region on purpose. From India use ap-south-1 (Mumbai): lowest latency, and your data stays in India. Set it as your default and check the Region name at the top right of the console before every create.
- Know how to shut down. Delete what you created, in dependency order, and check the Billing page the next day. If you finish with AWS, you can close the account from the account settings.
Worked example. Asha signs up on 1 March. She receives USD 100 and earns USD 40 more by launching an EC2 instance and using other activities, so she holds USD 140. If she burns USD 20 of it in labs, USD 120 remains. The plan still ends on 1 September at the latest, because 6 months is the cap. After 90 more days she must upgrade or lose the account, so she saves her lab notes in her own repository, not only in AWS.
Common mistake. Creating resources in the wrong Region and then forgetting them. The console shows only the current Region, so a forgotten NAT gateway in Virginia is invisible while you look at Mumbai. Check the bill by service, not just the resources you can see.
Exam trap. Certification questions about the shared responsibility model: AWS secures the cloud (hardware, facilities, hypervisor); you secure what you put in it (addressing, routes, security groups, patching, data). A Region is not an Availability Zone, and a VPC is regional, not global.
The forgotten lab
A student finished a tutorial, closed the laptop and forgot the NAT gateway she had built. Two weeks later a budget alert at 80 percent of her USD 5 limit landed in her inbox. She opened the Billing page, saw NAT Gateway hours and public IPv4 hours, deleted the gateway, released the Elastic IP and the bill stopped growing.
Lesson: the alert you set before the lab is what saved the month. Always delete in reverse order of creation.
"How do you protect a personal or lab AWS account from cost and security surprises?"
Strong answer: budget with email alert first; MFA on root and root unused; Identity Center or IAM user with least privilege; one chosen Region; tags on everything; and a written cleanup list. Mention that you check the Free plan terms because they changed in 2025.
Key takeaways
- A VPC is your private network inside one Region; subnets live in one AZ each.
- New accounts (after July 2025) get a Free plan: USD 100 credits plus up to USD 100 more, 6 months at most.
- Budget and alert first, MFA on root, no daily root use, Identity Center or an IAM user with MFA.
- Use ap-south-1 (Mumbai) from India and always check the Region before you create.
- Delete resources in dependency order when you finish.