Storage is one of the most fundamental building blocks of any cloud workload, and Amazon EBS (Elastic Block Store) makes it flexible to scale. Attaching a New EBS Volume to an EC2 Server Labs walks you through the complete lifecycle of adding extra block storage to a running instance — from creating the volume in the correct Availability Zone, to attaching it, to actually making it usable inside the operating system. Many users create an EBS volume and attach it via the console, only to find the extra space isn't accessible on their server. This lab closes that gap. You will practically go through identifying the correct Availability Zone, creating a volume with the right size and type, attaching it to a running EC2 instance, and then formatting, mounting, and persisting that mount inside the OS itself. This hands-on experience covers volume creation, attachment, filesystem creation, mounting, and configuring the volume to auto-mount on reboot using fstab — the same workflow used to add storage to production database servers, log servers, and application servers. Start right away to gain practical understanding and earn a certificate at the end.
No downtime or root volume risk — storage is expanded by adding a new volume, not resizing or touching the existing root disk. Workload isolation — logs, application data, or database files can live on their own volume, separate from the OS, making cleanup, backup, and troubleshooting easier. Reboot-safe configuration — using /etc/fstab with the nofail option ensures the mount persists across reboots without risking a boot failure if the volume is ever missing. Scalable by design — EBS volumes can be resized or replaced independently of the instance, so storage can grow with the application without re-provisioning the server.
Congratulations! In this lab, you successfully attached a new EBS volume to a running EC2 instance and made it fully usable from within the operating system. You created a volume in the correct Availability Zone, attached it to Backend-Server, formatted it with an ext4 filesystem, mounted it to a dedicated directory, and configured it to persist automatically across reboots using /etc/fstab.
This is one of the most common real-world storage operations in AWS — expanding an instance's capacity for logs, application data, or databases without touching the root volume or causing downtime. These skills form the foundation for managing scalable, resilient storage across any EC2-based workload.