AWS AWSEC2: Updated SSH connection phrasing in EC2 Instance Connect policy
Summary
Changed 'via ssh' to 'through SSH' for consistency and capitalization.
Security assessment
Minor wording update capitalizes 'SSH' and changes 'via' to 'through' without modifying security guidance or addressing vulnerabilities.
Evidence
+You can attach the `Ec2InstanceConnect` policy to your IAM identities. This policy grants permissions that allows customers to call EC2 Instance Connect to publish ephemeral keys to their EC2 instances and connect through SSH or the EC2 Instance Connect CLI.
Diff
diff --git a/AWSEC2/latest/UserGuide/security-iam-awsmanpol.md b/AWSEC2/latest/UserGuide/security-iam-awsmanpol.md index 81a15b423..60da23ec3 100644 --- a//AWSEC2/latest/UserGuide/security-iam-awsmanpol.md +++ b//AWSEC2/latest/UserGuide/security-iam-awsmanpol.md @@ -104 +104 @@ To view the permissions for this policy, see [EC2FastLaunchServiceRolePolicy](ht -You can attach the `Ec2InstanceConnect` policy to your IAM identities. This policy grants permissions that allows customers to call EC2 Instance Connect to publish ephemeral keys to their EC2 instances and connect via ssh or the EC2 Instance Connect CLI. +You can attach the `Ec2InstanceConnect` policy to your IAM identities. This policy grants permissions that allows customers to call EC2 Instance Connect to publish ephemeral keys to their EC2 instances and connect through SSH or the EC2 Instance Connect CLI.