Day 38 Getting Started with AWS Basics☁

Day 38 Getting Started with AWS Basics☁

IAM:

AWS Identity and Access Management (IAM) is a web service that helps you securely control access to AWS resources. With IAM, you can centrally manage permissions that control which AWS resources users can access. You use IAM to control who is authenticated (signed in) and authorized (has permissions) to use resources.

image

Task1:

Create an IAM user with username of your own wish and grant EC2 Access. Launch your Linux instance through the IAM user that you created now and install jenkins and docker on your machine via single Shell Script.

1 . Create an IAM User:

  • Go to the IAM dashboard in the AWS Management Console.

  • Click on "Users" in the right side click on "Create user"

  • Choose a "username" of your choice and select "Provide user access to the "AWS Management Console" and select "I want to create an IAM user" and then "Custom password" and type your own password and click on "Next".

  • Now "Set permissions" dashboard will open on that select "Attach policies directly" and search for "AmazonEC2FullAccess" policy to this user to grant EC2 access then click on "Next" and again click on "Create user".

NOTE: Make sure to save the "Access Key ID" and "Secret Access Key" for later use.

2 . Launch a Linux Instance:

Note: Copy your "Console sign-in URL" , "User name" , "Console password" in Notepad or click on "Download .csv file"

  • Before launching a instance we need to login to our IAM user account.

  • Copy your "Console sign-in URL" and past it on your "private window".

  • After that "Sign in as IAM user" dashboard will open in that we have to give our IAM "User name" and "Console password" which your copied in your notepad and click on "Sign in".

  • After that it will ask to change "old password " to "new password" change it to your requirement and click on *"*Confirm password " change.

Task2:

In this task you need to prepare a devops team of avengers. Create 3 IAM users of avengers and assign them in devops groups with IAM policy.