Skip to content

Commit 2e1bc52

Browse files
committed
updates
1 parent 4def549 commit 2e1bc52

File tree

1 file changed

+28
-0
lines changed

1 file changed

+28
-0
lines changed

lab-019/README.md

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# Lab-019
2+
3+
## Connection to an EC2 Instance via Systems Manager
4+
5+
Difficulty Level: 1
6+
7+
Creation Date: June 28, 2020
8+
9+
Original Author(s): [Thyago Mota](https://github.com/thyagomota)
10+
11+
Contributor(s):
12+
13+
## Goal
14+
This lab illustrates how to connect to an EC2 instance via [Systems Manager](https://aws.amazon.com/systems-manager/), a service that offers a central place to view and manage AWS resources.
15+
16+
## Overview
17+
18+
### Step 1 - Create a Role
19+
20+
Create a role named *EC2RoleForSystemsManager* to be attached to the EC2 instance so it can use the Systems Manager service. Go to *IAM - Roles - Create Role*. Select *AWS Service* as the trusted entity (i.e., the entity that can assume the role). Then choose *EC2* as the use case. Click *Next: Permissions*. Next select *AmazonSSMFullAccess* policy and click *Next: Tags* and then *Next: Review*. Conclude by giving a name for your role (*EC2RoleForSystemsManager*) and a description. Make sure you save the role.
21+
22+
### Step 2 - Launch Instance
23+
24+
If you choose *Amazon Linux 2 AMI* it already comes with the SSM agent pre-installed. In step 3 (Configure Instance), make sure to select the IAM role you created previously. Therefore, your EC2 instance will have the ability to use the *EC2RoleForSystemsManager* role. Because we will be using Systems Manager to connect to our instance, we don't even have to enable ssh access this time.
25+
26+
## Test and Validation
27+
28+
Go to *Systems Manager - Managed Instances*, select your EC2 instance and, using the actions drop-down menu, start a session to connect to your instance via Systems Manager.

0 commit comments

Comments
 (0)