search

aws / aws-elastic-beanstalk-cli

The EB CLI is a command line interface for Elastic Beanstalk that provides interactive commands that simplify creating, updating and monitoring environments from a local repository.
Apache License 2.0
162 stars 78 forks source link

Support SSH to private IP #3

Open alexjurkiewicz opened 4 years ago

alexjurkiewicz commented 4 years ago

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request. If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Tell us about your request

Add an option to eb ssh to always SSH to the internal IP if it exists. OR If the instance has no public address, SSH to the internal IP (rather than internal hostname).

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?

Our instances exist in private networks and the internal hostname cannot be resolved outside. However we have set up a VPN which allows developers to run ssh 10.1.1.1 from their local machine and connect to EB instances. However, eb ssh by default uses the internal AWS hostnames like ip-10-1-1-1.ap-northeast-1.compute.internal which do not resolve outside the VPC.

Are you currently working around this issue?

Wrote our own shell script to do this.

How are you currently solving this problem?

Additional context

Anything else we should know?

Place to implement fix: https://github.com/aws/aws-elastic-beanstalk-cli/blob/ad4f92cf1be6fbb0d2b1e365514a6c5e5c1b144d/ebcli/operations/sshops.py#L86

Attachments

If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information).

ChaseAllbee commented 4 years ago

Hey Alex,

Thanks for your input and the feature request, this is a good callout for eb ssh. We can take a look at the requirements and see if this is something we can add to our roadmap.

blampe commented 3 years ago

However we have set up a VPN which allows developers to run ssh 10.1.1.1 from their local machine and connect to EB instances. However, eb ssh by default uses the internal AWS hostnames like ip-10-1-1-1.ap-northeast-1.compute.internal which do not resolve outside the VPC.

We worked around this by disabling split tunneling on our VPN, but we'd very much like to re-enable it!

dehjli85 commented 1 year ago

Any updates on if this is going to be implemented?

brandonburkett commented 1 year ago

Check in on this too! With public IPv4 charges, it would be nice to have ssh with private IP support.