How to access Linux AWS EC2 instance from Windows

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.

1. Open the Amazon EC2 instance details page and copy the Public IPv4 DNS or Public IPv4 address value.

   Instances without a public address require a VPN, bastion host, or proxy path to reach port 22.

2. Restrict the instance security group inbound rule for SSH to port 22 from the Windows network public IP range.

   Setting the SSH source to 0.0.0.0/0 exposes the instance to internet-wide scanning and brute-force attempts.

3. Convert the AWS .pem private key to a PuTTY .ppk key using PuTTYgen.

   Anyone with the private key can authenticate as the permitted account; store the key in a protected location and avoid sharing it.

   Related: How to convert PEM key to PPK on Windows

4. Download PuTTY from the official website.

   https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html

5. Launch PuTTY.
6. Enter the instance address in Host Name (or IP address) and confirm Port is 22.
7. Enter a label under Saved Sessions and click Save.

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

8. Go to Connection → SSH → Auth from the sidebar menu.
9. Click on the Browse button to look for the PuTTY Private Key.
10. Select the .ppk private key file and click Open.
11. Click on the Open button to start the connection.
12. Review the host key fingerprint prompt and click Yes to cache the key when the fingerprint is trusted.

    Caching an untrusted host key can enable man-in-the-middle interception; verify the fingerprint before accepting.

    Related: How to edit known hosts key fingerprint for PuTTY

13. Enter the instance username and press Enter at the login prompt.

    Default usernames vary by AMI, with common values including ec2-user and ubuntu.

14. Enter the passphrase for the key if prompted.

    No passphrase prompt typically indicates the .ppk key was saved without encryption during conversion.

15. Confirm the remote shell prompt is displayed after authentication.