Using EC2 Roles and Instance Profiles in AWS

Table of Contents

1. Challenge

   Upload a File to the Amazon S3 bucket and Copy the Bucket ARN

   Choose any file you have locally, or you can optionally download the lab diagram locally, and upload it to the provided Amazon S3 bucket in you AWS account. Be sure to also copy the S3 bucket ARN for later on.

2. Challenge

   Connect to the Old EC2 and Locate the Hardcoded Credentials

   Leverage Session Manager to connect to the Old Server Amazon EC2 instance and locate the hardcoded set of AWS secret access key credentials for ssm-user. There should be an access key pair, as well as a configuration for output and Region.

3. Challenge

   Create the Managed Permissions Policy

   Create a new permission policy with the following information:

   • Name: allow-ec2-to-app-bucket
   • Permissions: List buckets and get objects from the S3 bucket that was created for you (Should be named like c6e0-account_id-app-bucket)
4. Challenge

   Create the IAM Role and Attach Permissions

   Create a brand-new IAM role with the following information:

   • Name: ec2-to-s3-role
   • Description: Whatever you want!
   • Trusted entity type: Amazon EC2
   • Permissions: Attach the allow-ec2-to-app-bucket policy you created, and attach the AmazonSSMManagedInstanceCore AWS managed policy
5. Challenge

   Attach the IAM Role to the New EC2 Instance

   Take the newly created ec2-to-s3-role IAM role and attach it to your New Server EC2 instance.

6. Challenge

   Get the File From Amazon S3 on the New EC2 Instance

   Connect to the New Sever Amazon EC2 instance via session manager. Use the AWS CLI to get the recently uploaded file from your Amazon S3 bucket and save it to the /tmp directory.