AWS neptune documentation change
Summary
Replaced 'AWS CloudFormation' with 'CloudFormation' in SSH connection instructions
Security assessment
Change is a terminology update. The existing security guidance about PEM file permissions (chmod 400) remains unchanged and was not modified in this diff.
Diff
diff --git a/neptune/latest/userguide/get-started-connect-ec2-same-vpc.md b/neptune/latest/userguide/get-started-connect-ec2-same-vpc.md index 31caf90d0..ad1400666 100644 --- a//neptune/latest/userguide/get-started-connect-ec2-same-vpc.md +++ b//neptune/latest/userguide/get-started-connect-ec2-same-vpc.md @@ -17 +17 @@ After creating the Amazon EC2 instance, you can log into it using SSH and connec -If you are using a Linux or macOS command line to connect to the EC2 instance, you can paste the SSH command from the **SSHAccess** item in the **Outputs** section of the AWS CloudFormation stack. You must have the PEM file in the current directory and the PEM file permissions must be set to 400 (`chmod 400 `keypair.pem``). +If you are using a Linux or macOS command line to connect to the EC2 instance, you can paste the SSH command from the **SSHAccess** item in the **Outputs** section of the CloudFormation stack. You must have the PEM file in the current directory and the PEM file permissions must be set to 400 (`chmod 400 `keypair.pem``).