The Challenge Begins

When I first received the DevOps Stage 0 task to set up NGINX on a fresh Ubuntu server, I’ll admit, I felt a mix of excitement and nervousness. As someone new to cloud deployments, the idea of configuring a web server on Google Cloud’s free tier seemed like a mountain to climb. But hey, every expert was once a beginner, right?

Step 1: Diving into Google Cloud

Creating a Virtual Machine (VM) on Google Cloud was my first hurdle. I remember staring at the Google Cloud Console, feeling a bit overwhelmed by all the options. But I took a deep breath and decided to tackle it step by step:

I logged into Google Cloud Console, feeling like I was entering a high-tech command center.
Found my way to Compute Engine → VM Instances (easier said than done on my first try!).
The “Create Instance” button was my gateway to the cloud. I clicked it and started configuring:
- Chose the e2-micro machine type (thank goodness for free tier options!)
- Selected Ubuntu 22.04 LTS as my trusty OS
- Checked the Allow HTTP traffic box (little did I know this wasn’t the end of my firewall adventure)
With a mix of hope and uncertainty, I hit “Create”.

Step 2: Meeting NGINX

With my VM up and running, it was time to make friends with NGINX. I connected via SSH, feeling like a hacker in a movie (even though I was just using Google Cloud Console).

I typed in the magic words:

sudo apt update 
sudo apt install -y nginx

Watching the installation process, I couldn’t help but feel a sense of accomplishment. “I’m really doing this,” I thought.

Then came the moment of truth - starting NGINX:

sudo systemctl start nginx
sudo systemctl enable nginx

I checked its status, half-expecting an error:

systemctl status nginx

And there it was - “active (running)”. I may have done a little victory dance in my chair.

Step 3: Customizing My Corner of the Web

Now came the fun part - making this server my own. I decided to add a personal touch to the default page:

sudo bash -c 'echo "Welcome to DevOps Stage 0 - MJ" > /var/www/html/index.html'

Seeing my name on that page felt like planting a flag on a newly discovered land. Small step for the internet, giant leap for this budding DevOps engineer!

Step 4: The Great Firewall Challenge

Remember when I thought checking “Allow HTTP traffic” during VM creation was enough? Oh, how naive I was. When I couldn’t access my page, I felt that familiar sinking feeling in my stomach. But then I remembered - troubleshooting is part of the job!

After some frantic Googling and head-scratching, I discovered the need to configure Google Cloud Firewall rules manually. It felt like solving a puzzle, and when I finally got it right, the sense of achievement was immense.

Step 5: The Moment of Truth

With trembling fingers, I typed my VM’s External IP into my browser. The moment the page loaded with my custom message, I let out a cheer that probably startled my neighbors. I did it! My very own web server, live on the internet!

Challenges: My DevOps Baptism by Fire

The Firewall Fiasco: This was my first real taste of cloud security. It taught me that in the cloud, what you can’t see can definitely hurt you (or at least block your web traffic).
NGINX’s Disappearing Act: After a VM reboot, finding NGINX gone felt like losing a friend. The relief when I figured out how to make it stick around (sudo systemctl enable nginx) was palpable.
Permission Denied - The Humbler: Nothing says “you still have much to learn” like a permission denied error. It was a valuable lesson in Linux file permissions and the power of sudo.

What I Learned (Besides the Technical Stuff)

Patience is a DevOps virtue. Things rarely work on the first try, and that’s okay.
The importance of celebrating small victories. Each problem solved is a step forward.
Google is a DevOps engineer’s best friend. Knowing how to search for solutions is a skill in itself.
The DevOps community is incredibly helpful. I’m not alone in this journey.

Looking Ahead

This experience has opened my eyes to the vast world of cloud infrastructure. I’m excited to dive deeper into:

Mastering cloud platforms like Google Cloud
Exploring the intricacies of web servers and networking
Learning more about automation and scalability

References

During this task, I explored career paths related to cloud infrastructure:

Final Thoughts

Setting up NGINX on Google Cloud Free Tier was more than just a technical exercise - it was a journey of self-discovery. I faced challenges, experienced moments of doubt, but ultimately emerged with new skills and a boosted confidence.

To anyone starting their DevOps journey: embrace the challenges, celebrate the victories (no matter how small), and remember - every expert you admire started exactly where you are now. Keep pushing, keep learning, and who knows? Maybe one day, you’ll be writing about setting up complex microservices architectures with the same excitement I feel about this simple NGINX server.

Onwards and upwards in the cloud!

My Journey: Setting Up NGINX on Google Cloud Free Tier