Mistakes to Avoid While Mounting AWS EBS Volume on Ubuntu EC2 Linux Instance

Sumit Jha — Sun, 08 Feb 2026 17:26:07 +0000

Yes, I was doing the simple and basic EBS Volume creation and mounting it. But I got stuck in the 1st point itself.

What is it?

Checking the availability zone.

Yes, this simple mistake will take you hours to debug. So, let’s start from the basics of creating volume and mounting it.

How to Create EBS Volume In AWS?

Step 1 - Start Your Instance in which you want to add a volume.

Go to EC2 Dashboard » Select the instance » Action » Start » Click Volumes under Elastic Block Store

You will be redirected to the Volumes Section.

Step 2 - Creating EBS Volumes

This is the very simple yet most confusing part.

Then you will be directed to a page where we can create the volumes.

And there is the most common mistake I made while creating the EBS Volumes, which we will see.

Select the size of the disk that you want to add
Select the availability zone.

The rest of the things you can keep as the default.

The Mistake that I Made While Selecting an Availability Zone

Selecting the wrong Availability Zone.

Yes, the mistake looks small, but it will totally ruin your time.

I know that I have to select an Availability zone that matches my instances. So I checked the availability zone as per the screenshot.

So, I checked at 1 and thought any of us-east-1 zone. But there are mutliple option to choose from. But I selected the default one., i.e., us-east-1a. and proceed with creating the volumes.

However on going forward, when it comes to attaching the volumes to my instance, I couldn’t simply find my instances.

On checking, everything seems fine, however, it is not working.

How To Find Out the Correct “Availability Zone”

This is a very simple and important set.

Go back instances.
Select Your Instance
Click On Networking

Check Availability Zone

Now you have your correct “Availability Zone“, you can create Volumes once again with the correct Availability Zone.

Summing Up

Creating an Volume without correct availability zone will not work. You have to find correct zone before you can proceed for next step.

I hope you have enjoyed my article and will implement this into your project.

From Funnels to Pipelines: Why I’m Trading Digital Marketing for DevOps

Sumit Jha — Sat, 17 Jan 2026 20:02:40 +0000

After 5+ years in Digital Marketing, I’ve decided to make a major pivot. I’m shifting my career focus toward DevOps.

To my marketing colleagues, this might sound like I’m moving to a different planet. To my future tech colleagues, it might look like I’m a "non-tech" outsider. But here is the truth: Marketing and DevOps are built on the same DNA.

Why the Shift?

In Marketing, I obsessed over Automation. I spent my days building email funnels and lead workflows to make sure no user was dropped. In DevOps, that same "workflow" mindset applies—only instead of moving leads through a funnel, I’m moving code through a pipeline.

I’m moving to DevOps because I want to build the systems that make the products, rather than just selling them. The "Technical Debt" we feel in marketing operations—broken APIs, slow landing pages, and siloed data—is exactly what DevOps is designed to solve.

My 6-Month Roadmap (2026 Edition)

I don’t believe in "overnight" success. I’ve laid out a rigorous 4–6 month plan to become job-ready while balancing my current role.

Month 1: The Foundation (Linux & Networking)
Goal: Move away from the GUI. I’m spending my first month in the terminal (Ubuntu).

Key Skills: Bash scripting, SSH, DNS, and the OSI model. If you can’t navigate a server, you can't automate it.

Month 2: The "Version Control" Phase (Git & Python)
Goal: Treat "Infrastructure as Code."

Key Skills: Mastering Git workflows. I’m also picking up Python to automate the repetitive tasks that used to take me hours in marketing spreadsheets.

Month 3: Containerization (Docker)
Goal: "It works on my machine" should never be an excuse.

Key Skills: Learning to package applications into Docker containers so they run anywhere—from my laptop to the cloud.

Month 4-5: Cloud & Orchestration (AWS & Kubernetes)
Goal: Scaling for millions.

Key Skills: I’ll be focusing on AWS (specifically EC2, S3, and IAM) and learning how Kubernetes manages container clusters at scale. This is the "Big Leagues" of DevOps.

Month 6: The "Project" Phase & Career Bridging
Goal: Build a portfolio that speaks both languages.

Outcome: I plan to build a "Full-Stack Observability" project, showing how system performance directly impacts Marketing Conversion Rates.

Final Thoughts

Transitioning isn't about throwing away my marketing experience; it's about upgrading the toolkit. I’m still focused on the "Customer Journey," but now I’m ensuring that journey happens on a fast, secure, and unbreakable infrastructure.

Forem: Sumit Jha