image_genrated_using_chatgpt

KodeKloud AWS Challenge — Day 50: Expanding an EC2 Root Volume Without Downtime

Safely increasing EBS storage from 8 GiB to 12 GiB and extending the root filesystem live.

Introduction

Running out of disk space is not a theoretical problem — it’s a production outage waiting to happen.

Day 50 focused on expanding the root volume of an EC2 instance:

• Instance: datacenter-ec2
• Current size: 8 GiB
• Required size: 12 GiB
• No downtime allowed
• Root (/) must reflect the new size

This is real infrastructure management — not just provisioning.

Step 1: Identify the Attached Volume

From the AWS Console:

1. Navigate to EC2 → Instances
2. Select datacenter-ec2
3. Open the Storage tab
4. Note the Volume ID

Then verify under:

EC2 → Elastic Block Store → Volumes

Confirm:

• Size = 8 GiB
• State = In-use
• Attached to datacenter-ec2

You are modifying the root EBS volume.

Step 2: Modify the EBS Volume Size

In EBS → Volumes:

1. Select the volume
2. Click Actions → Modify Volume
3. Change size:

• 8 GiB → 12 GiB

4. Save

AWS allows online EBS resizing.

Wait until:

State = Optimizing or Completed

You do NOT need to stop the instance.

Step 3: SSH Into the Instance

From the AWS client host:

ssh -i /root/datacenter-keypair.pem ubuntu@<public-ip>

Or:

ssh -i /root/datacenter-keypair.pem ec2-user@<public-ip>

(Depending on AMI)

Verify current disk size:

lsblk
df -h

You’ll see:

• Volume = 12 GiB
• Root partition still showing 8 GiB

This is expected.

AWS resized the block device — not the filesystem.

Step 4: Expand the Partition

First, check partition layout:

lsblk

If root device is:

/dev/xvda1

Run:

sudo growpart /dev/xvda 1

This expands partition 1 to use the full disk.

If growpart is missing:

sudo apt install cloud-guest-utils -y

Step 5: Resize the Filesystem

Now expand the filesystem.

If using ext4:

sudo resize2fs /dev/xvda1

If using xfs:

sudo xfs_growfs -d /dev/xvda1

Most modern Ubuntu Amazon Linux AMIs use xfs.

Step 6: Verify Expansion

Run:

df -h

Now root (/) should reflect:

12G total

Storage expansion complete.

Why This Works Without Downtime

Amazon EBS supports:

• Online volume modification
• Live filesystem resizing
• Zero instance restart (in most cases)

The process:

1. Expand block storage
2. Extend partition
3. Grow filesystem

Three layers. All must be handled.

Common Failure Points

• Forgetting to grow partition
• Forgetting to resize filesystem
• Wrong device name
• Not waiting for volume modification to complete
• Using incorrect filesystem command (xfs vs ext4)

Disk resizing has 3 layers: Block → Partition → Filesystem

Miss one, and it won’t reflect.

Key Takeaways

• EBS resizing is safe and live
• Filesystem expansion is manual
• Always verify with df -h
• Know your filesystem type
• Infrastructure maintenance requires precision

Cloud doesn’t eliminate ops — it changes it.