From Learning EC2 to Launching My First Web Server
Today I decided to take what I learned about Amazon EC2 and put it into practice.
Reading about EC2 and actually launching a server are two different experiences. So instead of stopping with the theory, I wanted to create an instance and see the process for myself.
What I wanted to build
My goal was simple:
Launch an EC2 instance → Configure access → Connect to the server → Install a web server → Access it through the internet
It wasn't a large project, but it helped me understand how the different parts fit together.
Step 1: Launching an EC2 Instance
I started by launching an EC2 instance from the AWS Console.
While going through the configuration, I came across several concepts that I had previously learned about, such as the instance type, key pair, and networking settings.
Seeing these options while actually creating a server made the concepts much easier to understand.
An EC2 instance is essentially a virtual server that I can create and manage in the AWS Cloud.
Step 2: Configuring the Security Group
The next important step was configuring the security group.
A security group controls the network traffic that can reach my EC2 instance.
For my web server, I needed to allow the appropriate web traffic. This helped me understand why security groups are important instead of simply thinking of them as another configuration option.
One thing I learned from this was:
«A server can be running correctly, but that doesn't necessarily mean it is reachable from the internet.»
The network rules also need to allow the required traffic.
Step 3: Connecting to the Instance
After launching the instance, I connected to it and started working with the server.
This was one of the moments where the learning became more practical. Instead of seeing EC2 as just an AWS Console resource, I was now interacting with an actual cloud server.
I could run commands and configure the environment just like I would with a server.
Step 4: Installing a Web Server
Once connected, I installed a web server on the EC2 instance.
The purpose was simple: I wanted my EC2 instance to actually serve something rather than just exist as a running virtual machine.
After the installation and configuration, I was able to test the web server.
This helped me understand the basic relationship between:
EC2 → Web Server → Network Access → Web Browser
What I Learned from the Hands-On Experience
The biggest difference between theory and hands-on practice is that every concept starts connecting with the others.
Before this exercise, I understood EC2 as a service that provides virtual servers.
After doing it myself, I understood the basic workflow much better:
Launch an instance
↓
Configure security rules
↓
Connect to the server
↓
Install and configure software
↓
Allow the required network traffic
↓
Access the application
I also realized that launching an EC2 instance is only the beginning. There are many other things to understand, especially security, networking, monitoring, and cost management.
What's Next?
This hands-on exercise has motivated me to explore EC2 further.
Next, I want to understand how EC2 works with VPC, subnets, public and private IP addresses, IAM roles, and load balancers.
I also want to deploy a small application instead of only a basic web server.
Final Thoughts
Today's practice was a small step, but it made AWS feel much more real to me.
Instead of only learning what EC2 is, I actually created a server, configured access to it, connected to it, and used it to run a web server.
I'm learning that the best way for me to understand AWS is:
Learn → Practice → Make mistakes → Fix them → Learn again.
This is just one hands-on step in my AWS journey, and I'm looking forward to seeing what I can build next.
Loading article