How to Create Your First Server on AWS (Step-by-Step)

Amazon Web Services (AWS) makes it incredibly easy — and often free — to spin up your very first virtual server (called an EC2 instance) in minutes. Whether you’re a developer testing an app, a student learning cloud computing, or a small business owner needing a reliable web server, EC2 gives you full control over a virtual machine in the cloud.

IIn this detailed, beginner-friendly guide (updated for 2026), we’ll walk through every single step using the AWS Management Console. We’ll use the Free Tier so you won’t pay a cent if you’re eligible. By the end, you’ll have a running Linux server you can connect to via SSH, and you’ll know exactly how to shut it down safely.

application, or learn the fundamentals of cloud computing, creating your first server on AWS is the perfect place to start.

This guide will walk you through every step of the process, from setting up your AWS account to launching and connecting to your very first virtual server, known as an EC2 instance. We’ll also cover crucial tips for managing costs so you can experiment with confidence.

Why Launch Your First Server on AWS?

Scalable & powerful: Start small and grow instantly.
Free Tier: 750 hours/month of a t3.micro (or similar) instance for new accounts.
Global: Choose a region close to your users.
Secure by default: Built-in firewalls, key-pair login, and more.

Important Free Tier Note (2026): If your AWS account was created before July 15, 2025, you get 750 hours of t2.micro or t3.micro per month for 12 months. If created on or after July 15, 2025, you get t3.micro/t3.small/t4g.micro/etc. plus up to $200 in credits for the first 6 months. Always terminate your instance when done to avoid charges.

Prerequisites

Before we begin, make sure you have:

An AWS account (free to create).
A computer with internet.
An SSH client (built-in on Mac/Linux; use PuTTY or Windows Terminal on Windows).
Administrator access to your AWS account.

Don’t have an AWS account yet? Go to https://aws.amazon.com/free/, click Create an AWS Account, enter your email, choose “Personal” or “Professional”, verify your email/phone, and add a payment method (you won’t be charged if you stay in Free Tier).

Step 1: Log In to the AWS Management Console

Open your browser and go to https://console.aws.amazon.com/.
Sign in with your root user email and password (or IAM user if you created one).
At the top-right, select a Region close to you (e.g., US East (N. Virginia) or Europe (Ireland)). This matters for latency and pricing.

Step 2: Open the EC2 Dashboard

In the search bar at the top, type EC2 and click EC2 under Services.
You’re now on the EC2 Dashboard. Click the big orange Launch instance button in the “Launch instance” pane.

Step 3: Launch Your First EC2 Instance (The Wizard)

The Launch an instance wizard appears. We’ll use mostly defaults but choose Free Tier options.

3.1 Name and Tags

Under Name and tags, enter a Name like My-First-Server.
(Optional) Add a tag: Key = Environment, Value = Test.

3.2 Application and OS Images (Amazon Machine Image)

Choose Quick Start tab.
Select Amazon Linux (recommended for beginners — it’s free-tier eligible and lightweight).
Make sure the AMI shows “Free tier eligible” badge.

3.3 Instance Type

Under Instance type, select t3.micro (or t2.micro if available).
It should show “Free tier eligible”. This gives you 1 vCPU and 1 GB RAM — perfect for your first server.

3.4 Key Pair (Login)

Under Key pair (login), click Create new key pair.
Name it MyFirstKey.
Choose .pem (for SSH).
Click Create key pair.
The .pem file downloads automatically — save it somewhere safe (e.g., ~/Downloads/MyFirstKey.pem). Never share this file!

3.5 Network Settings

Leave VPC and Subnet as default.
Under Security group, the default group is created automatically.
Edit the inbound rules if needed:
- Type: SSH
- Source: My IP (recommended for security) or Anywhere (0.0.0.0/0) for quick testing.
Leave everything else default.

3.6 Configure Storage

Default 8 GiB gp3 volume is perfect for starters. Leave as-is.

3.7 Summary & Launch

On the right panel, review everything.
Click the big blue Launch instance button.
You’ll see a green Success banner with your instance ID (starts with i-).

Step 4: Wait for Your Server to Start

Click View all instances (or go to the left menu → Instances).
Find your instance by name.
Refresh every few seconds until:
- Instance state = Running
- Status checks = 2/2 checks passed
Note your Public IPv4 address or Public IPv4 DNS (you’ll need this to connect).

Step 5: Connect to Your Server via SSH

On Mac/Linux:

Open Terminal.
Navigate to your key file folder:Bashcd ~/Downloads chmod 400 MyFirstKey.pem
Connect:Bashssh -i MyFirstKey.pem ec2-user@your-public-ip-address(Replace your-public-ip-address with the one from the console.)

On Windows:

Use Windows Terminal, PowerShell, or PuTTY.

First Login:

Type yes when asked about the host fingerprint.
You’re in! You’ll see a welcome message.

Run these first commands to update your server:

Bash

sudo yum update -y
sudo yum install -y httpd
sudo systemctl start httpd
sudo systemctl enable httpd

Congratulations — you now have a live web server in the cloud!

Step 6: (Optional) Test Your Server

Visit http://your-public-ip-address in your browser. You should see the Amazon Linux test page (or Apache default if you installed httpd).

Step 7: Clean Up — Terminate Your Instance

Never leave instances running if you’re not using them.

Back in the EC2 console, select the checkbox next to your instance.
Click Instance state → Terminate (delete) instance.
Confirm by clicking Terminate (delete).
The instance will go to Shutting-down then disappear.

Tip: Use Stop instead of Terminate if you want to keep the instance for later (it still costs a tiny amount for storage).

Common Issues & Troubleshooting

“Permission denied” on SSH → Run chmod 400 your-key.pem.
Connection timeout → Check security group allows SSH from your IP; wait 2–3 minutes after launch.
Charges appearing → Check the EC2 Free Tier box on the dashboard. Terminate immediately.
Key pair lost → You can’t recover it. Launch a new instance with a new key.

Best Practices for Your Next Servers

Always use IAM users instead of root.
Restrict security groups to specific IPs.
Enable termination protection.
Use stop for temporary servers.
Explore AWS Lightsail for even simpler servers later.

This server is now your personal sandbox in the cloud. From here, you can install software like a web server (Apache or Nginx), host a website, or set up a database. The possibilities are endless. Happy building

Next Steps

Launch a Windows instance (use RDP instead of SSH).
Install Docker or a web app (WordPress, Node.js).
Try Auto Scaling, Load Balancers, or S3 storage.
Take the free AWS Cloud Practitioner course.

You just created and connected to your first AWS server — that’s a huge milestone! The cloud is now your playground.

Have questions? Drop them in the comments. Want me to cover connecting with PuTTY, installing a LAMP stack, or launching a Windows server next? Let me know!

Stay safe & happy clouding! 🚀

Last updated: March 2026 Official AWS Documentation used: Launch an EC2 instance and Free Tier tracking. Always check the console for the absolute latest UI.