What security measures should you apply to migration traffic to AWS?

• A. Encrypt in transit (TLS), secure endpoints, enforce IAM permissions, and use VPN/Direct Connect with network security.
• B. Disable encryption to speed transfer.
• C. Store credentials in plaintext.
• D. Open all ports to the internet.

Answer: (A)

Protecting migration traffic to AWS hinges on securing data in transit, authenticating endpoints, enforcing strict access controls, and using private network connections. Encrypting in transit with TLS keeps data unreadable if it’s intercepted during transfer. Connecting to secure endpoints—using HTTPS/TLS and validating certificates—prevents connecting to forged or malicious destinations. Enforcing IAM permissions ensures only authorized users and services can initiate or manage migration tasks, applying the principle of least privilege. Using a VPN or AWS Direct Connect with proper network security (and restricting access with security groups and network ACLs) provides a private, monitored path for migration traffic, reducing exposure to the public internet.

Disabling encryption to speed transfers is unsafe because it exposes sensitive data. Storing credentials in plaintext is a critical secret leak risk. Opening all ports to the internet creates an easy target for attacks.