100 days of AWS cloud (Day1)

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

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

: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

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

: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

: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