Day 1 of my 100 Days AWS Cloud Challenge with KodeKloud
Today I worked on AWS basics and successfully created an EC2 Key Pair (RSA) for secure access to instances.
Learned:
Small step, but building strong fundamentals!
#DevOps #AWS #CloudComputing #KodeKloud #100DaysOfDevOps
if you face any issue refer to these tutorials where i tried to explain every task in detail GitHub - MiqdadProjects/KodeKloud-100-Days-Of-AWS: 100 Days of AWS Cloud Challenge | KodeKloud Engineer task solutions with step-by-step explanations and YouTube tutorials. · GitHub
Day 2 of my 100 Days DevOps Challenge with KodeKloud
Today I worked with AWS and created a Security Group for application servers.
Configured:
Key Learning:
Security Groups in AWS act as a stateful firewall at the instance level, controlling inbound and outbound traffic.
In real-world scenarios, SSH access is usually restricted to specific IP ranges for better security.
Step by step, building strong cloud fundamentals!
#DevOps #AWS #CloudSecurity #KodeKloud #100DaysOfDevOps
FELL FREE TO EXPLORE MY SOLUTION STAR THE REPO PLEASEE
Day 3 – AWS Subnet
Created a subnet (nautilus-subnet) under the default VPC.
Details:
Learning:
A subnet must belong to a specific AZ and should not overlap with existing subnets in the VPC.
172.31.0.1
172.31.16.0
172.31.32.0
172.31.48.0
172.31.64.0
172.31.80.0
So I assigned next CIDR block 172.31.96.0. Also I got to know how to quickly calculate number of subnets VPC CIDR is /16 and subnets is /20 means So the number of subnets is:
2(20−16)=2^4 = 16 subnets
Question:
How do companies design subnet strategies for large-scale production environments?
superb rdk keep on doing hands on tasks 
Day 4 – AWS S3 Versioning
Enabled versioning on the S3 bucket devops-s3-2904.
Learning:
Versioning keeps multiple variants of an object in the same bucket, which helps recover data if files are deleted or overwritten accidentally.
This gave me a practical understanding of how AWS handles backup and recovery at the storage level.
Thank Yu Miqdad your help and guidance means a lot 
Day 5 – AWS EBS GP3 Volume
Created an EBS volume named devops-volume with:
Learning:
EBS volumes provide persistent block storage for EC2 instances, similar to virtual hard disks.
Also understood how AWS uses the Name tag behind the scenes for resource naming in the console.
Day 6 – AWS EC2 Instance Launch
Successfully launched an EC2 instance named datacenter-ec2 using:
Learning:
Launching an EC2 instance is not just clicking a button — it combines compute selection, SSH authentication setup, and security group association.
Also observed the AWS status checks process before the instance becomes fully available.
Day 7 – AWS EC2 Instance Type Modification
Modified the EC2 instance type and ensured it returned to running state successfully.
Learning:
AWS EC2 instances can be resized according to workload demands. This helps in better cost utilization and infrastructure optimization.
Also understood the exact sequence required:
Day 8 – AWS EC2 Stop Protection
Enabled stop protection on the EC2 instance devops-ec2 in us-east-1.
Learning:
AWS provides operational safeguards like stop protection to prevent accidental shutdown of critical workloads.
Also got clarity on the distinction between:
Day 9 – AWS EC2 Termination Protection
Enabled termination protection on the EC2 instance devops-ec2 in us-east-1.
Learning:
AWS provides termination protection as a safeguard against accidental deletion of important cloud servers.
This helped me understand that infrastructure management is not just about provisioning resources, but also about protecting business-critical systems from human mistakes.
Day 10 – AWS Elastic IP Association
Associated an Elastic IP with the EC2 instance in us-east-1.
Learning:
Elastic IPs provide static public addresses for EC2 instances, ensuring connectivity remains consistent even after instance restarts.
Also understood how AWS maps an Elastic IP to the private network interface of an EC2 instance.
Day 11 of my 100 Days DevOps Challenge with KodeKloud
Today I worked with AWS Elastic Network Interfaces (ENI) and attached an additional network interface to an EC2 instance.
Instance: xfusion-ec2
Network Interface: xfusion-eni
Key Learning:
An Elastic Network Interface acts like a virtual network card for an EC2 instance. It allows AWS instances to have:
Day 12 – AWS EBS Volume Attachment
Attached the volume nautilus-volume to the EC2 instance nautilus-ec2 using device name /dev/sdb.
Learning:
AWS EBS volumes provide detachable persistent storage that can be connected to EC2 instances based on workload needs, how volumes can be attached dynamically
This gave me practical understanding of:
fantastic work if you any help regarding these tasks you can refer to this playlist
https://www.youtube.com/watch?v=nUJUjftQ1pg&list=PLAdSxQAWkF-kDCfisdWgbGyX1l3HcTjBw
Day 13 – AWS AMI Creation
Created an AMI named xfusion-ec2-ami from the EC2 instance xfusion-ec2 and verified the AMI reached available state successfully.
Learning:
Amazon Machine Images allow us to capture a complete reusable image of an EC2 server, making cloning, backup, and standardized deployments much easier.
This helped me understand how AWS supports:
Day 14 – AWS EC2 Instance Termination
Terminated the EC2 instance and verified the instance reached terminated state successfully.
Learning:
Infrastructure management also includes identifying and removing obsolete resources to optimize cloud utilization and reduce unnecessary costs.
Also got clarity on:
Will definitely watch out .Thanks