AWS AWSEC2 documentation change
Summary
Updated SCP documentation to recommend rsync over SSH for security and efficiency
Security assessment
The change emphasizes using encrypted rsync over SSH instead of plaintext rsync, promoting secure file transfer practices but does not address a specific vulnerability.
Diff
diff --git a/AWSEC2/latest/UserGuide/linux-file-transfer-scp.md b/AWSEC2/latest/UserGuide/linux-file-transfer-scp.md index f3ad1dfa0..fb98cfb73 100644 --- a//AWSEC2/latest/UserGuide/linux-file-transfer-scp.md +++ b//AWSEC2/latest/UserGuide/linux-file-transfer-scp.md @@ -7 +7 @@ -One way to transfer files between your local computer and a Linux instance is to use the secure copy protocol (SCP). This section describes how to transfer files with SCP. The procedure is similar to the procedure for connecting to an instance with SSH. +One way to transfer files between your local computer and a Linux instance is to use the secure copy protocol (SCP). SCP is a good option for simple operations, such as as one-time file copies. SCP secures files transfers using the same .pem file that you use to connect to an instance using SSH. If you need to keep files synchronized, or if the files are large, **rsync** is faster and more efficient than SCP. For security, use **rsync** over SSH, as **rsync** transfers data using plain text by default.