Search for a command to run...
"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
No comments yet. Be the first to comment.
This series documents my 100 Days of Cloud journey with AWS using KodeKloud. Each blog covers one daily task with hands-on practice, simple explanations, and real learning for beginners and cloud aspirants.
During the migration process, several resources were created under the AWS account. Later on, some of these resources became obsolete as alternative solutions were implemented. Similarly, there is an
One of the most common networking issues in AWS occurs when an EC2 instance is correctly configured but remains inaccessible from the internet. Even if the security group, network ACLs, and applicatio
Static websites are one of the simplest and most cost-effective ways to host web content in the cloud. Instead of managing virtual machines or web servers, Amazon S3 allows you to store HTML, CSS, Jav
Containerization has become the standard way to package and deploy modern applications. Instead of installing software directly on virtual machines, developers package everything—including dependencie
On Day 37 of the KodeKloud 100 Days of Cloud Challenge, I explored one of the AWS security best practices—granting an EC2 instance access to Amazon S3 using IAM Roles instead of storing AWS credential
On Day 36 of the KodeKloud 100 Days of Cloud Challenge, I built a complete Application Load Balancer (ALB) architecture on AWS. Instead of exposing an EC2 instance directly to the internet, an Applica
Anand Raval
136 posts
I'm Anand Raval, a Cloud & DevOps Engineer with AWS Solutions Architect Associate (SAA-C03), Certified Kubernetes Administrator (CKA), and Azure Fundamentals (AZ-900) certifications. This blog covers AWS, Kubernetes, Terraform, CI/CD, cloud architecture, automation, cost optimization, troubleshooting guides, and hands-on DevOps projects.
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.
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
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
I opened the AWS Management Console and selected the us-east-1 region.
From the EC2 console:
EC2 → Elastic Block Store → Volumes
I searched for the volume named: xfusion-vol
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.
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.
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.