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.
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 17 of the KodeKloud 100 Days of Cloud Challenge, I worked with another important IAM feature in AWS: IAM Groups.
In the previous lab, I created an IAM user. However, managing permissions individually for every user can become difficult as the number of users grows. AWS IAM Groups help solve this problem by allowing multiple users to be managed together and assigned permissions as a group.
In this lab, the objective was to create an IAM group named iamgroup_kirsty.
An IAM Group is a collection of IAM users.
Instead of attaching permissions to each user separately, permissions can be assigned to a group, and all users within that group inherit those permissions automatically.
IAM Groups are commonly used to organize users based on their roles, such as:
Developers
DevOps Engineers
Database Administrators
Security Teams
Read-Only Users
This makes permission management much easier in larger AWS environments.
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 → User Groups
This section displays all existing IAM groups within the AWS account.
I clicked on Create Group and entered the following details:
| Field | Value |
|---|---|
| Group Name | iamgroup_kirsty |
For this lab, no policies needed to be attached. After reviewing the information, I created the group.
After the group was created, I checked the User Groups section and confirmed that iamgroup_kirsty appeared in the list.
This verified that the task had been completed successfully.
This lab helped me understand why IAM Groups are useful when managing multiple users.
Creating a group may seem like a small task, but it becomes extremely valuable when an organization has dozens or even hundreds of users. Instead of updating permissions user by user, administrators can manage permissions at the group level.
This approach reduces operational effort and helps maintain consistent access control across teams.
In production AWS environments, IAM Groups are commonly used to organize users based on their job responsibilities.
For example:
Developers may belong to a Developer Group
DevOps Engineers may belong to a DevOps Group
Auditors may belong to a ReadOnly Group
Permissions are assigned to the group, and every member automatically receives the appropriate access level.
This approach follows AWS security best practices and simplifies user management.
Day 17 introduced IAM Groups, an important feature for managing user permissions efficiently in AWS.
While the task only involved creating a single group, it demonstrated how AWS helps organizations scale access management as teams grow. Understanding IAM users and groups is a key step toward building secure and well-organized AWS environments.
As I continue the KodeKloud 100 Days of Cloud Challenge, I am gaining hands-on experience with the core AWS services that are used daily in real-world cloud infrastructure.