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

Connect to AWS EC2 instance without SSH, only via AWS SSM #8186

Closed
serverhorror opened this issue Mar 13, 2023 · 11 comments
Closed

Connect to AWS EC2 instance without SSH, only via AWS SSM #8186

serverhorror opened this issue Mar 13, 2023 · 11 comments
Labels
feature-request Request for new features or functionality ssh Issue in vscode-remote SSH
Milestone

Comments

@serverhorror
Copy link

serverhorror commented Mar 13, 2023

I did look for "ssm" or "aws" issues, none seem to apply.

There is a discussion in aws/aws-toolkit-vscode#941. A lot of people, including myself, would like to be able to use AWS SSM directly instead of tunneling SSH thru SSM.

Is it possible to provide a hook so the community can create this or even add this directly?

Thank you so much!

@serverhorror serverhorror changed the title Connect to EC2 instance without SSH, only via SSM Connect to AWS EC2 instance without SSH, only via AWS SSM Mar 13, 2023
@github-actions github-actions bot added the ssh Issue in vscode-remote SSH label Mar 14, 2023
@serverhorror
Copy link
Author

serverhorror commented Mar 14, 2023

Just to be clear: I think this is not labeled correctly.

It should not work via SSH.

@eleanorjboyd eleanorjboyd added the feature-request Request for new features or functionality label Mar 17, 2023
@VSCodeTriageBot VSCodeTriageBot added this to the Backlog Candidates milestone Mar 17, 2023
@VSCodeTriageBot
Copy link
Collaborator

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 10 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@justinmk3
Copy link

@VSCodeTriageBot
Copy link
Collaborator

🙂 This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@roblourens
Copy link
Member

This seems to be an aws-specific feature, right? I don't think it makes sense to provide built-in support for this. If it helps, an extension could probably build this on top of Remote-SSH, and you would still have to tunnel ssh over ssm, but you could probably get a more streamlined experience.

@justinmk3
Copy link

This seems to be an aws-specific feature, right? I don't think it makes sense to provide built-in support for this.

To avoid aws-specific solution, some sort of extensibility is needed, perhaps one of the issues I linked above.

If it helps, an extension could probably build this on top of Remote-SSH, and you would still have to tunnel ssh over ssm, but you could probably get a more streamlined experience.

Isn't that prohibited by the license?

You cannot create other extensions that extend or manipulate the Remote Development extensions.

@roblourens
Copy link
Member

I don't think this is what is meant by "build my own product or service". But I'm not a lawyer and I'll try to get a better answer for you. Will have to be after the holidays though.

@serverhorror
Copy link
Author

serverhorror commented Dec 20, 2023

This seems to be an aws-specific feature, right? I don't think it makes sense to provide built-in support for this. If it helps, an extension could probably build this on top of Remote-SSH, and you would still have to tunnel ssh over ssm, but you could probably get a more streamlined experience.

That's badly phrased on my end.

I want to be able for extension authors to provide a custom connection method. Currently only SSH works.

Situations:

  • we have a bastion host that requires custom commands to connect next to the final hop
  • We use AWS SSM
  • connect to a shell a container in Kubernetes
  • Connect to shell to an ephemeral Container in Kubernetes
  • Connect to a shell in a singularity container
  • ...

Does that make more sense?

@roblourens
Copy link
Member

I get it, I think we aren't interested in supporting a custom connection method, supporting ssh is complex enough as it is. We have the 3 extensions for WSL, Containers, and ssh, and ssh can do a lot.

@justinmk3
Copy link

justinmk3 commented Dec 21, 2023

Sure, but what about providing before/after hooks for the ssh case?

@v-au
Copy link

v-au commented Jan 3, 2024

I get it, I think we aren't interested in supporting a custom connection method, supporting ssh is complex enough as it is. We have the 3 extensions for WSL, Containers, and ssh, and ssh can do a lot.

There are main differences between SSH and AWS SSM which makes the latter the preferred choice for AWS customers.
SSH requires the remote to have SSH configured (service, keys). AWS SSM requires none of that. Additionally, AWS SSM doesn't require a network port to be open on the host. Yes, you can do SSH over SSM but that is a band-aid solution..

@microsoft microsoft locked and limited conversation to collaborators Feb 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality ssh Issue in vscode-remote SSH
Projects
None yet
Development

No branches or pull requests

6 participants