100 days of AWS cloud (Day1)

Cloud AWS
#7

:date: Day 4 – AWS S3 Versioning

Enabled versioning on the S3 bucket devops-s3-2904.

:closed_lock_with_key: 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.

1 Like
#8

Thank Yu Miqdad your help and guidance means a lot :+1: :heartbeat:

#9

:date: Day 5 – AWS EBS GP3 Volume

Created an EBS volume named devops-volume with:

  • gp3 type
  • 2 GiB size

:bulb: 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.

#10

:date: Day 6 – AWS EC2 Instance Launch

Successfully launched an EC2 instance named datacenter-ec2 using:

  • Amazon Linux AMI
  • t2.micro instance type
  • RSA key pair (datacenter-kp)
  • default security group

:bulb: 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.

1 Like
#11

:date: Day 7 – AWS EC2 Instance Type Modification

Modified the EC2 instance type and ensured it returned to running state successfully.

:bulb: 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:

  1. stop instance
  2. change instance type
  3. restart and verify status checks
#12

:date: Day 8 – AWS EC2 Stop Protection

Enabled stop protection on the EC2 instance devops-ec2 in us-east-1.
:bulb: Learning:
AWS provides operational safeguards like stop protection to prevent accidental shutdown of critical workloads.

Also got clarity on the distinction between:

  • stop protection → prevents stopping
  • termination protection → prevents deletion
#13

:date: Day 9 – AWS EC2 Termination Protection
Enabled termination protection on the EC2 instance devops-ec2 in us-east-1.
:bulb: 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.

#14

:date: Day 10 – AWS Elastic IP Association

Associated an Elastic IP with the EC2 instance in us-east-1.

:bulb: 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.

#15

:rocket: 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.
:desktop_computer: Instance: xfusion-ec2
:electric_plug: Network Interface: xfusion-eni
:bulb: Key Learning:
An Elastic Network Interface acts like a virtual network card for an EC2 instance. It allows AWS instances to have:

  • additional private/public IPs
  • multiple network paths
  • traffic separation for management or application needs
    Also learned the importance of correct device indexing while attaching secondary interfaces.
    This gave me practical understanding of AWS networking beyond just security groups and Elastic IPs.
#16

:date: Day 12 – AWS EBS Volume Attachment
Attached the volume nautilus-volume to the EC2 instance nautilus-ec2 using device name /dev/sdb.
:bulb: 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:

  • volume lifecycle states (available / in-use)
  • attaching storage to live compute resources
  • device mapping concepts in AWS
#17

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

1 Like
#18

:date: 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.
:bulb: 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:

  • infrastructure templating
  • disaster recovery
  • rapid server provisioning
#19

:date: Day 14 – AWS EC2 Instance Termination
Terminated the EC2 instance and verified the instance reached terminated state successfully.
:bulb: Learning:
Infrastructure management also includes identifying and removing obsolete resources to optimize cloud utilization and reduce unnecessary costs.
Also got clarity on:

  • instance shutdown lifecycle
  • normal terminate vs force terminate
  • importance of waiting for final terminated state before validation
1 Like
#20

Will definitely watch out .Thanks :+1:

1 Like
#21

:date: Day 15 – AWS EBS Snapshot Creation
Created a snapshot and verified the snapshot reached completed state successfully.
:bulb: Learning:
EBS snapshots are incremental backups that help in:

  • disaster recovery
  • data restoration
  • creating new volumes
  • infrastructure backup strategies
    This task also gave practical understanding of snapshot lifecycle and validation timing in AWS.
#22

:date: Day 16 – AWS IAM User Creation
Created an IAM user successfully in AWS IAM.
:bulb: Learning:
AWS IAM is the foundation of cloud security and access management. It helps control authentication and authorization:

  • who can access AWS
  • what resources they can use
  • what actions they are allowed to perform
    This task also gave me exposure to the updated AWS IAM user creation workflow in the AWS console.
#23

:date: Day 17 – AWS IAM Group Creation
Created an IAM group successfully in AWS IAM.
:bulb: Learning:
IAM Groups provide centralized permission management for multiple AWS users.
This helped me understand how organizations structure access control by grouping users based on:

  • teams
  • departments
  • job responsibilities
#24

:date: Day 18 – AWS IAM Policy Creation
Created a custom IAM policy that provides read-only access to EC2 resources like:

  • instances
  • AMIs
  • snapshots
    :bulb: Learning:
    IAM policies are the core permission mechanism in AWS and control:
  • allowed actions
  • accessible resources
  • security boundaries
    This task also helped me understand how EC2 Describe APIs are used to provide read-only console visibility.
#25

:date: Day 19 – AWS IAM Policy Attachment
Attached the IAM policy to the IAM user successfully.
:bulb: Learning:
IAM policies are what actually grant permissions in AWS. Without policies, IAM users have little or no access to resources.
This task gave practical understanding of:

  • Direct permission assignment
  • Policy attachment workflows
  • AWS access control structure
#26

:date: Day 20 – AWS IAM Role Creation
Created an IAM role

  • Trusted Entity: AWS Service (EC2)
  • Attached Policy
    :bulb: Learning:
    IAM Roles allow AWS services like EC2 to securely access other AWS resources using temporary credentials instead of hardcoded access keys.
    This task helped me better understand:
  • trust relationships
  • role assumption
  • policy attachment to roles
  • secure AWS access patterns
1 Like