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

allow ability to pass optional custom parameters to aws emr ssh/socks #1799

Closed
kirkhansen opened this issue Feb 17, 2016 · 7 comments
Closed
Labels
closed-for-staleness emr feature-request A feature should be added or improved.

Comments

@kirkhansen
Copy link

I would like to be able to run a proxy command via command line options when running aws emr ssh or emr socks.

An example request could look something like:

aws emr ssh --cluster-id j-3SD91U2E1L2QX --key-pair-file ~/.ssh/mykey.pem -o ProxyCommand='ssh firewall_jump -W %h:%p'

where you could have as many -o's as you please.

It would also be beneficial to allow custom ports for the -D option.

@jamesls
Copy link
Member

jamesls commented Feb 25, 2016

It also we worth seeing if we could also just print out the ssh command to stdout so a user could modify it as they need to. Something like: $(aws emr ssh-command --cluster-id ...) -o ProxyCommand='ssh'

@jamesls jamesls added feature-request A feature should be added or improved. emr labels Feb 25, 2016
@JordonPhillips
Copy link
Member

The issue with the above is that we create a file if putty is being used. Otherwise it would be a trivial change.

@ASayre
Copy link
Contributor

ASayre commented Feb 6, 2018

Good Morning!

We're closing this issue here on GitHub, as part of our migration to UserVoice for feature requests involving the AWS CLI.

This will let us get the most important features to you, by making it easier to search for and show support for the features you care the most about, without diluting the conversation with bug reports.

As a quick UserVoice primer (if not already familiar): after an idea is posted, people can vote on the ideas, and the product team will be responding directly to the most popular suggestions.

We’ve imported existing feature requests from GitHub - Search for this issue there!

And don't worry, this issue will still exist on GitHub for posterity's sake. As it’s a text-only import of the original post into UserVoice, we’ll still be keeping in mind the comments and discussion that already exist here on the GitHub issue.

GitHub will remain the channel for reporting bugs.

Once again, this issue can now be found by searching for the title on: https://aws.uservoice.com/forums/598381-aws-command-line-interface

-The AWS SDKs & Tools Team

@ASayre ASayre closed this as completed Feb 6, 2018
@salmanwaheed
Copy link

salmanwaheed commented Feb 6, 2018 via email

@salmanwaheed
Copy link

salmanwaheed commented Feb 6, 2018 via email

@jamesls jamesls reopened this Apr 6, 2018
@jamesls
Copy link
Member

jamesls commented Apr 6, 2018

Based on community feedback, we have decided to return feature requests to GitHub issues.

@github-actions
Copy link

Greetings! It looks like this issue hasn’t been active in longer than one year. We encourage you to check if this is still an issue in the latest release. Because it has been longer than one year since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment to prevent automatic closure, or if the issue is already closed, please feel free to reopen it.

@github-actions github-actions bot added closing-soon This issue will automatically close in 4 days unless further comments are made. closed-for-staleness and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels Sep 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-for-staleness emr feature-request A feature should be added or improved.
Projects
None yet
Development

No branches or pull requests

5 participants