Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EC2 Remote from Windows : ec2_connect.ps1 missing #6248

Open
ojacques opened this issue Dec 16, 2024 · 4 comments
Open

EC2 Remote from Windows : ec2_connect.ps1 missing #6248

ojacques opened this issue Dec 16, 2024 · 4 comments
Labels
bug We can reproduce the issue and confirmed it is a bug. platform:windows service:ec2

Comments

@ojacques
Copy link

Problem

When trying the new experimental feature to "connect to EC2 instance in a new Remote window" from Windows, the script ec2_connect.ps1 is missing.

image

Logs :

2024-12-16 13:36:48.386 [error] aws.ec2.openRemoteConnection: Error: Failed to update connect script [ConnectScriptUpdateFailed]
	 -> EntryNotFound (FileSystemError): Error: ENOENT: no such file or directory, open 'c:\Users\[redacted]\.vscode\extensions\amazonwebservices.aws-toolkit-vscode-3.39.0\resources\ec2_connect.ps1' [FileNotFound]

Steps to reproduce the issue

  1. Start VSCode on Windows, with AWS Toolkit 3.39
  2. Enable experimental feature "ec2RemoteConnect"
  3. Browse to an EC2 in AWS Toolkit explorer
  4. Click the button "connect to EC2 instance in a new Remote window"
  5. The error is shown

Expected behavior

I should be able to open a new VSCode window, connected to this remote EC2 through SSM.

System details (run AWS: About and/or Amazon Q: About)

  • OS: Windows 11
  • Visual Studio Code version: 1.96.0
  • AWS Toolkit version: 3.39.0
  • Amazon Q version: NA
@ojacques ojacques added the bug We can reproduce the issue and confirmed it is a bug. label Dec 16, 2024
@justinmk3
Copy link
Contributor

Connecting from Windows is not yet implemented. We plan to follow up on this.

@ojacques
Copy link
Author

Connecting from Windows is not yet implemented. We plan to follow up on this.

Thanks! So I should not expect being able to connect from WSL on Windows to a remote EC2 either? The error is different, but I'm leaving it here:

Connecting to Dev Environment requires the Remote SSH extension ('ms-vscode-remote.remote-ssh' of version >=0.74.0) to be installed and enabled.

despite the Remote SSH extension being installed (v 0.116.0).

@justinmk3
Copy link
Contributor

justinmk3 commented Dec 16, 2024

So I should not expect being able to connect from WSL on Windows to a remote EC2 either? The error is different, but I'm leaving it here:

If you started vscode from WSL and are running the WSL (Linux) version of vscode, it should work. If you are connecting to WSL from Windows, then that is a "remote" situation which isn't currently supported (it would require remote-ssh in the remote (WSL) vscode instance, plus AWS Toolkit would need to understand this and invoke vscode in the correct way, which currently is not supported).

despite the Remote SSH extension being installed (v 0.116.0).

Is it installed in the remote WSL environment (not your local desktop vscode code)?

@ojacques
Copy link
Author

If you started vscode from WSL

Yes, from WSL, running code .

and are running the WSL (Linux) version of vscode, it should work.

Indeed, no. VSCode is installed on Windows, with the remote extension, which I understand is not supported at the moment.

Feel free to close this issue as this is unsupported for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug We can reproduce the issue and confirmed it is a bug. platform:windows service:ec2
Projects
None yet
Development

No branches or pull requests

2 participants