From 18bdcd5fcce1bd0b2f55b3852f7ba383e1137652 Mon Sep 17 00:00:00 2001 From: John Culkin Date: Mon, 31 Jan 2022 16:47:55 -0500 Subject: [PATCH] Update README.md --- 106-Connecting-to-EC2-Instances-Using-Session-Manager/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/106-Connecting-to-EC2-Instances-Using-Session-Manager/README.md b/106-Connecting-to-EC2-Instances-Using-Session-Manager/README.md index 80591e2..ee838cd 100644 --- a/106-Connecting-to-EC2-Instances-Using-Session-Manager/README.md +++ b/106-Connecting-to-EC2-Instances-Using-Session-Manager/README.md @@ -7,7 +7,7 @@ You have an EC2 instance in a private subnet and need to connect to the instance ## Solution Create an IAM role, attach the `AmazonSSMManagedInstanceCore` policy, create an EC2 instance profile, attach the IAM role you created to the instance profile, associate the EC2 instance profile to an EC2 instance, and finally, run the `aws ssm start-session` command to connect to the instance. A logical flow of these steps is shown in Figure 1-8. -![Figure 1.8](ConnectingToEC2InstancesUsingAWSSSMSession Manager.png) +![Figure 1.8](/ConnectingToEC2InstancesUsingAWSSSMSession Manager.png) Prerequisites * Amazon Virtual Private Cloud (VPC) with isolated or private subnets and associated route tables