As we covered the basics of AWS and IAM on Day 38, let's continue from where we left off.

Task-1:

• Launch EC2 instance with already installed Jenkins on it. Once server shows up in console, hit the IP address in browser and you Jenkins page should be visible.

• Take screenshot of Jenkins page, this will verify the task completion.

Solution:

As Jenkins runs on port 8080, you need to edit security groups to allow connection requests on port 8080.

• 

  

  

  

  Jenkins has already been covered. You can refer to Day-22 for more details.

Task-2:

• Learn more about IAM Users, Groups and Roles.

• Create three Roles named: DevOps-User, Test-User and Admin.

IAM Users

IAM Users are individual identities with specific permissions. Think of them as individual accounts for people or applications that need to interact with AWS. Each user has unique credentials (like a username and password) and can have specific permissions assigned to them. For example, you might create an IAM user for each member of your DevOps team, each with different levels of access based on their role.

IAM Groups

IAM Groups are collections of IAM users. They help manage permissions for multiple users at once. Instead of assigning permissions to each user individually, you can assign permissions to a group, and all users in that group inherit those permissions. For instance, you might have a “Developers” group with permissions to access development resources and a “Admins” group with broader access.

IAM Roles

IAM Roles are a bit different. They are not tied to a specific user but can be assumed by anyone or anything that needs them. Roles are used to grant temporary access to AWS resources. For example, an EC2 instance might assume a role to access S3 buckets without needing to store credentials on the instance itself. Roles are also useful for cross-account access, where resources in one AWS account need to be accessed by another account.

Summary

• Users: Individual identities with specific permissions.

• Groups: Collections of users with shared permissions.

• Roles: Temporary access permissions that can be assumed by users, applications, or services.

Solution:

1. Go to IAM > Roles > Create role.

2. Choose EC2 for service or use case, Click Next.

3. On Add permissions add AmazonEC2ReadOnlyAccess, Click Next.

   

4. Add role name as mentioned in a task and click Create role.

   

5. And you will see the newly created role.

   

Follow the same procedure for Test-User and Admin and add the permissions as you like.

Thank you for reading😉.