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.
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 u
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 16 of the KodeKloud 100 Days of Cloud Challenge, I worked with AWS Identity and Access Management (IAM), one of the most important services in AWS.
Whenever we create infrastructure in AWS, managing access becomes a critical task. Instead of sharing the root account with everyone, AWS provides IAM to create users and control what actions they can perform.
In this lab, the objective was simple: create a new IAM user named iamuser_james.
AWS Identity and Access Management (IAM) is a service that helps manage access to AWS resources securely.
Using IAM, we can:
Create users for different team members
Assign permissions through policies
Organize users into groups
Create roles for services and applications
Follow security best practices by avoiding root account usage
One thing I have noticed while learning AWS is that IAM is usually one of the first services configured in a new AWS account because every other service depends on proper access control.
The requirement for this task was straightforward:
I logged in to the AWS Management Console and searched for IAM.
From the AWS services menu, I opened the IAM Dashboard.
From the left navigation menu, I selected:
IAM → Users
This section displays all IAM users available in the account.
I clicked on Create User and entered the following details:
| Field | Value |
|---|---|
| User Name | iamuser_james |
After reviewing the information, I proceeded with the user creation process.
Once the user was created, I verified that iamuser_james appeared in the Users list.
This confirmed that the task was completed successfully.
Although this was a simple task, it reinforced an important AWS concept.
Instead of using the root account for daily operations, IAM users should be created for individuals who need access to AWS resources.
In real-world environments, IAM users are typically assigned permissions through IAM Groups and Policies, ensuring that users only have access to the resources they actually need.
In production environments, organizations often have multiple developers, DevOps engineers, and administrators working within the same AWS account.
IAM helps enforce the principle of least privilege, where each user receives only the permissions required to perform their job.
This improves security and reduces the risk of accidental changes.
Day 16 introduced another foundational AWS concept through IAM user management.
While creating an IAM user may seem like a small task, it is one of the building blocks of AWS security. Understanding IAM is essential because every AWS service relies on proper authentication and authorization.
As I continue the KodeKloud 100 Days of Cloud Challenge, I am gaining practical experience with the services that form the foundation of cloud infrastructure.