AWS AWSEC2 documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' and clarified permissions requirements for parameter deletion
Security assessment
Changes are primarily branding updates (removing redundant 'AWS' prefix) and clarifying existing IAM permission requirements. No specific security vulnerability is addressed, though it improves documentation accuracy around required ssm:DeleteParameter permissions.
Diff
diff --git a/AWSEC2/latest/UserGuide/create-key-pairs.md b/AWSEC2/latest/UserGuide/create-key-pairs.md index 9a64c51ce..b2eff9cd8 100644 --- a//AWSEC2/latest/UserGuide/create-key-pairs.md +++ b//AWSEC2/latest/UserGuide/create-key-pairs.md @@ -5 +5 @@ -Create a key pair using Amazon EC2Create a key pair using AWS CloudFormationImport a public key to Amazon EC2 +Create a key pair using Amazon EC2Create a key pair using CloudFormationImport a public key to Amazon EC2 @@ -110 +110 @@ Use the [New-EC2KeyPair](https://docs.aws.amazon.com/powershell/latest/reference -When you create a new key pair using AWS CloudFormation, the private key is saved to AWS Systems Manager Parameter Store. The parameter name has the following format: +When you create a new key pair using CloudFormation, the private key is saved to AWS Systems Manager Parameter Store. The parameter name has the following format: @@ -117 +117 @@ For more information, see [AWS Systems Manager Parameter Store](https://docs.aws -###### To create a key pair using AWS CloudFormation +###### To create a key pair using CloudFormation @@ -144 +144 @@ The following is example output. -To enable AWS CloudFormation to manage Parameter Store parameters on your behalf, the IAM role assumed by AWS CloudFormation or your user must have the following permissions: +To enable CloudFormation to manage Parameter Store parameters on your behalf, the IAM role assumed by CloudFormation or your user must have the following permissions: @@ -148 +148 @@ To enable AWS CloudFormation to manage Parameter Store parameters on your behalf - * `ssm:DeleteParameter` – Grants permission to delete the parameter that stored the private key material. This permission is required whether the key pair was imported or created by AWS CloudFormation. + * `ssm:DeleteParameter` – Grants permission to delete the parameter that stored the private key material. This permission is required whether the key pair was imported or created by CloudFormation. @@ -153 +153 @@ To enable AWS CloudFormation to manage Parameter Store parameters on your behalf -When AWS CloudFormation deletes a key pair that was created or imported by a stack, it performs a permissions check to determine whether you have permission to delete parameters, even though AWS CloudFormation creates a parameter only when it creates a key pair, not when it imports a key pair. AWS CloudFormation tests for the required permission using a fabricated parameter name that does not match any parameter in your account. Therefore, you might see a fabricated parameter name in the `AccessDeniedException` error message. +When CloudFormation deletes a key pair that was created or imported by a stack, it performs a permissions check to determine whether you have permission to delete parameters, even though CloudFormation creates a parameter only when it creates a key pair, not when it imports a key pair. CloudFormation tests for the required permission using a fabricated parameter name that does not match any parameter in your account. Therefore, you might see a fabricated parameter name in the `AccessDeniedException` error message.