Secure access to a Linux AWS EC2 instance from Windows enables administration, troubleshooting, and deployment over an encrypted channel while avoiding password-based remote logins.
Access is typically provided by SSH on port 22 using public-key authentication, where the downloaded .pem private key corresponds to a public key installed on the instance for the target account, and PuTTY uses its own .ppk key container that requires conversion before connecting.
Connectivity also depends on a reachable address (public IP/DNS or an internal path via VPN/bastion/proxy), an inbound security group rule that permits port 22 from the correct source IP range, and the correct default username for the chosen AMI. Restricting inbound rules reduces exposure to scanning and brute-force attempts, and host key warnings should only be accepted after verifying the fingerprint from a trusted source.
Instances without a public address require a VPN, bastion host, or proxy path to reach port 22.
Setting the SSH source to 0.0.0.0/0 exposes the instance to internet-wide scanning and brute-force attempts.
Anyone with the private key can authenticate as the permitted account; store the key in a protected location and avoid sharing it.
https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html


Saving a session preserves the host, port, and authentication settings for future logins.




Caching an untrusted host key can enable man-in-the-middle interception; verify the fingerprint before accepting.
Default usernames vary by AMI, with common values including ec2-user and ubuntu.
No passphrase prompt typically indicates the .ppk key was saved without encryption during conversion.
