Fix SSH Key Permissions

### Solution: Change File Permissions on Windows WSL

1. **Navigate to the directory containing your `gotoapp.pem` file**:

cd /path/to/your/key

2. **Check the current permissions** (to confirm):

ls -l gotoapp.pem

3. **Change the permissions of your `.pem` file**:

chmod 600 gotoapp.pem

– The `600` permission means:
– Owner can read and write (`rw-`).
– No permissions for the group and others (`—`).

4. **Verify the new permissions**:

ls -l gotoapp.pem

You should see something like:

-rw------- 1 user user 1692 Nov 13 12:34 gotoapp.pem

5. **Try connecting to your EC2 instance again**:

ssh -i gotoapp.pem ubuntu@ec2-13-60-215-155.eu-north-1.compute.amazonaws.com

### Explanation
– SSH requires that private key files are only accessible by the owner to ensure security.
– On WSL, `chmod` works correctly for setting permissions, unlike on some native Windows file systems.

This should resolve the permission denied error and allow you to connect to your EC2 instance. Let me know if you encounter any other issues!

### Step-by-Step Solution

1. **Confirm You're in the Correct Directory**
Make sure you're in the directory where your `gotoapp.pem` file is located:

cd /path/to/your/key

2. **Check the File System Type**
If you're using WSL, and your `.pem` file is located on a Windows-mounted drive (e.g., `/mnt/c/`), the `chmod` command might not behave as expected due to Windows file system limitations. To check if you're on a Windows drive:

df -T /path/to/your/key

If it shows something like `drvfs`, it's a Windows-mounted drive. In this case, move your key to the WSL file system.

3. **Move the Key File to the WSL Home Directory**
To avoid permission issues, move the key file to your WSL home directory:

cp gotoapp.pem ~/gotoapp.pem
   cd ~

4. **Set the Correct Permissions Again**
Now that the key is in the WSL file system, set the permissions:

chmod 600 gotoapp.pem

5. **Try Connecting Again**
Use the moved key file for your SSH connection:

ssh -i ~/gotoapp.pem ubuntu@ec2-13-60-215-155.eu-north-1.compute.amazonaws.com

### Additional Troubleshooting

– **Use Verbose Mode for SSH**:
To get more details on why the connection is failing, use the `-v` option:

ssh -v -i ~/gotoapp.pem ubuntu@ec2-13-60-215-155.eu-north-1.compute.amazonaws.com

This will provide debug information that can help pinpoint the issue.

– **Check SSH Configurations**:
Make sure your SSH client is using the correct protocol and key type. You can force the key type with:

ssh -o IdentitiesOnly=yes -i ~/gotoapp.pem ubuntu@ec2-13-60-215-155.eu-north-1.compute.amazonaws.com

– **Remove the Host from Known Hosts (if needed)**:
Sometimes, SSH stores old fingerprints that can cause conflicts. Remove the host from the known hosts file:

ssh-keygen -R ec2-13-60-215-155.eu-north-1.compute.amazonaws.com

Let me know if any of these steps help resolve the issue!

### Solution 1: Using `wsl` SSH Configuration Adjustments

1. **Create or Edit the SSH Config File**:
Open the SSH config file in your WSL environment:

nano ~/.ssh/config

2. **Add the Following Configuration**:

Host ec2-instance
       HostName ec2-13-60-215-155.eu-north-1.compute.amazonaws.com
       User ubuntu
       IdentityFile ~/gotoapp.pem
       IdentitiesOnly yes
       StrictHostKeyChecking no

Save the file and exit (`Ctrl + X`, then `Y` to confirm, and `Enter`).

3. **Set Proper Permissions for the Config File**:

chmod 600 ~/.ssh/config

4. **Try Connecting Using the Alias**:

ssh ec2-instance

### Solution 2: Moving Key to WSL Home Directory

If you haven't already tried moving the key to your WSL home directory, this is a crucial step due to permission handling differences between Windows and WSL.

1. **Move the Key File to Your Home Directory**:

cp /mnt/c/path/to/gotoapp.pem ~/gotoapp.pem

2. **Set the Correct Permissions**:

chmod 600 ~/gotoapp.pem

3. **Attempt to SSH Again**:

ssh -i ~/gotoapp.pem ubuntu@ec2-13-60-215-155.eu-north-1.compute.amazonaws.com

### Solution 3: Running SSH from PowerShell with Elevated Permissions

If you need to use the `.pem` file directly from a Windows drive, try using PowerShell as Administrator.

1. **Open PowerShell as Administrator**:
– Press `Win + X` and select **Windows Terminal (Admin)** or **PowerShell (Admin)**.

2. **Use the Full Path for the `.pem` File**:

ssh -i "C:pathtogotoapp.pem" ubuntu@ec2-13-60-215-155.eu-north-1.compute.amazonaws.com

### Solution 4: Using `ssh-agent`

If permissions are still an issue, you can add the key to the `ssh-agent`:

1. **Start the SSH Agent**:

eval "$(ssh-agent -s)"

2. **Add Your Key to the Agent**:

ssh-add ~/gotoapp.pem

3. **Try Connecting Again**:

ssh ubuntu@ec2-13-60-215-155.eu-north-1.compute.amazonaws.com

### Solution 5: Convert the `.pem` File to `ppk` for Use with PuTTY (Optional)

If you prefer using PuTTY on Windows:

1. Download and open **PuTTYgen**.
2. Load your `.pem` file.
3. Save it as a `.ppk` file.
4. Use PuTTY to connect using the `.ppk` file.

—

These solutions should help you resolve the SSH permission issues on Windows 11 when using WSL. Let me know if you encounter further issues!