Merge pull request #54 from JaimePolop/patch-1

Update aws-ssm-privesc.md

pentesting-cloud/aws-security/aws-privilege-escalation/aws-ssm-privesc.md

@@ -71,7 +71,7 @@ In order to start a session you need the **SessionManagerPlugin** installed: [ht
 #### Privesc to ECS
 
 When **ECS tasks** run with **`ExecuteCommand` enabled** users with enough permissions can use `ecs execute-command` to **execute a command** inside the container.\
-According to [**the documentation**](https://aws.amazon.com/blogs/containers/new-using-amazon-ecs-exec-access-your-containers-fargate-ec2/) this is done by creating a secure channel between the device you use to initiate the “_exec_“ command and the target container with SSM Session Manager.\
+According to [**the documentation**](https://aws.amazon.com/blogs/containers/new-using-amazon-ecs-exec-access-your-containers-fargate-ec2/) this is done by creating a secure channel between the device you use to initiate the “_exec_“ command and the target container with SSM Session Manager. (SSM Session Manager Plugin necesary for this to work)\
 Therefore, users with `ssm:StartSession` will be able to **get a shell inside ECS tasks** with that option enabled just running:
 
 ```bash