AWS Day 15: Creating an Amazon EBS Volume Snapshot | KodeKloud 100 Days of Cloud
"I'm a 3rd-year Computer Engineering student at Marwadi University with skills in C++, web development (MERN stack), and DevOps tools like Kubernetes. I contribute to open-source projects and share tech knowledge on GitHub and LinkedIn. I'm learning cloud technologies and app deployment. As an Internshala Student Partner, I help others find jobs and courses." now currently focusing on #90DaysOfDevops
Introduction
During Day 15 of the KodeKloud 100 Days of Cloud Challenge, I have done some work in creating Amazon EBS snapshot. It is one of the ways that snapshots can be created in AWS for backing up EBS volumes and recovering data in cases of data loss through deletion, corruption, or failure of infrastructures.
This lab aims at creating a snapshot of an already existing EBS volume known as xfusion-vol within us-east-1 region.
What is an Amazon EBS Snapshot?
Amazon EBS Snapshot is a backup of an EBS volume that exists in Amazon S3. Amazon EBS Snapshots can be used for:
Backing up important data
Restoring deleted volumes
Creating new volumes out of existing data
Disaster Recovery strategies
Automation of the process of backup
Lab Objective
The requirements of this task were:
Creation of a snapshot of the existing EBS volume xfusion-vol
Name of the snapshot is xfusion-vol-ss
Description of the snapshot is xfusion Snapshot
Ensure the status of the snapshot is Completed
Steps Performed
Step 1: Navigate to the EC2 Dashboard
I opened the AWS Management Console and selected the us-east-1 region.
Step 2: Locate the EBS Volume
From the EC2 console:
EC2 → Elastic Block Store → Volumes
I searched for the volume named: xfusion-vol
Step 3: Create the Snapshot
I selected the volume and clicked:
Actions → Create Snapshot
Then I entered:
| Field | Value |
|---|---|
| Name | xfusion-vol-ss |
| Description | xfusion Snapshot |
After verifying the details, I created the snapshot.
Step 4: Verify Snapshot Creation
I navigated to:
EC2 → Snapshots
and monitored the snapshot status.
Initially the status showed:
Pending
After a short period, it changed to:
Completed
which confirmed that the snapshot was successfully created.
Conclusion
Day 15 introduced a fundamental AWS backup concept through Amazon EBS Snapshots. Although creating a snapshot is a simple task, it plays a critical role in protecting data and enabling recovery in real-world cloud environments.
As I continue the KodeKloud 100 Days of Cloud Challenge, I am gaining hands-on experience with core AWS services and operational best practices.
