AWS + Linux Combo — Part 2: Create AWS Account & Launch EC2
In this part, we go from zero to having a real Linux server running in AWS. This is where it gets concrete. By the end of this lesson, you will have an EC2 instance running, and you will be ready to connect to it in the next part.
Step 1: Create Your AWS Account
Go to aws.amazon.com and click "Create a Free Account". You will need to provide an email address, create a password, and choose an account name. During signup, AWS will ask for a credit card — this is required even for the free tier. AWS uses it to verify your identity and to charge you if you go beyond free tier limits. As long as you follow the lessons and clean up resources afterward, you will not be charged.
After entering your card details, AWS will ask you to verify your identity with a phone call or SMS. Complete this step. Then choose the Basic support plan — it is free and sufficient for learning.
Understanding the AWS Console
Once logged in, you see the AWS Management Console. This is the web interface for all AWS services. The top navigation shows your region in the top right corner. Region matters — all resources you create exist in a specific geographic region. For this series, choose a region close to you. For India, use ap-south-1 (Mumbai). Make sure you always have the right region selected before creating resources.
The search bar at the top lets you find any service quickly. Type "EC2" and click on it to go to the EC2 dashboard.
What is EC2?
EC2 stands for Elastic Compute Cloud. It is AWS's virtual server service. An EC2 instance is basically a computer running in an AWS data center that you can access over the internet. You choose how much CPU, memory, and storage it has. You choose the operating system. You start it, stop it, and delete it whenever you want. You pay by the hour (or second in some cases) for the time it is running.
Step 2: Launch Your First EC2 Instance
In the EC2 dashboard, click the orange "Launch instance" button. You will be taken through a setup wizard:
- Name your instance — Call it something like "my-first-server"
- Choose an AMI — Select "Amazon Linux 2023" (it is free tier eligible and well-optimized)
- Choose instance type — Select
t2.microort3.micro— these are free tier eligible - Create a Key Pair — Click "Create new key pair", name it "my-key", choose RSA and .pem format, click Create. Your browser will download a .pem file — save this file, you cannot download it again
- Network settings — Leave defaults, but make sure "Allow SSH traffic from" is set to "My IP"
- Storage — 8 GB default is fine
- Click Launch instance
Understanding Key Pairs
A key pair is how you authenticate to your Linux server. It uses public-key cryptography. AWS keeps the public key, and you keep the private key (the .pem file). When you SSH into the server, your private key proves your identity. Without this file, you cannot connect. Move it somewhere safe on your computer — many developers put it in a folder called ~/.ssh/.
chmod 400 ~/.ssh/my-key.pemOn Windows, you may need to adjust file permissions through Properties → Security.
Step 3: Check Your Running Instance
After launching, go to EC2 → Instances. You will see your instance listed. It takes about 1-2 minutes to start. The status will change from "pending" to "running". Once it says "running", your Linux server is live in the cloud.
Click on your instance to see its details. The most important fields right now are the Public IPv4 address or Public IPv4 DNS — you will use one of these to connect in the next lesson.
Understanding Security Groups
A Security Group is a virtual firewall for your EC2 instance. It controls which traffic is allowed in and out. When you launched the instance, AWS created a Security Group that allows SSH (port 22) from your IP. This means only your computer can connect to the server via SSH right now. Later in the series, we will open more ports when we deploy web applications.
Free Tier Reminder
The t2.micro instance is free for 750 hours per month for the first 12 months of your AWS account. Since a month has about 720-744 hours, running one instance continuously stays within the free tier. Running two instances doubles usage, which may incur charges. Always stop or terminate instances when you are done learning for the day to stay safe.
# Stop: saves the instance state, you can restart it later
# (storage still has a small cost, but EC2 hours stop counting)
# Terminate: permanently deletes the instance
# (use this when you are completely done with an instance)What We Accomplished
You now have a real Linux server running in Amazon's data center. It has a public IP address. It is connected to the internet. It is waiting for you to connect. In Part 3, we will SSH into this server from your local machine and start navigating the Linux environment inside it.
Building Cloud Intuition Over Time
Cloud computing is a domain where deep intuition — the ability to make good architectural decisions quickly, to diagnose problems efficiently, and to anticipate how systems will behave under load — develops through accumulated hands-on experience. Every project you build on cloud infrastructure teaches you something that cannot be learned from documentation alone. The cost surprises, the permission errors, the networking debugging sessions, the performance investigations — these are not obstacles to learning, they are the learning. The engineers who have built genuinely deep cloud intuition have usually accumulated it through many projects over several years, not from any single course or certification. Start building things, make mistakes safely in learning environments, and accumulate that experience deliberately.