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

aws emr create-cluster --configurations and web console settings are inconsistent #1678

Closed
fs111 opened this issue Dec 14, 2015 · 11 comments
Closed
Assignees
Labels
emr feature-request A feature should be added or improved. p3 This is a minor priority issue paramfile response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.

Comments

@fs111
Copy link

fs111 commented Dec 14, 2015

When creating a new EMR cluster on the cli, the emr commandline insists that the protocol for the configurations either being file:// of http(s)://. Using s3:// will not work. The web-console on the other hand demands that the protocol has to be s3://. That is inconsistent and confusing.

@rayluo
Copy link
Contributor

rayluo commented Dec 17, 2015

Thanks for bringing this to our attention.

The underlying API expects a raw json as input. Web console and CLI each provides a convenience on top of it to give customer a chance to load json content directly from a file. It turns out they implement different input format. Web console accepts s3://... only, while CLI traditionally accepts either file(b):// or http(s):// for almost any parameter. Current CLI implementation specifically documents this requirement already.

That being said, it is still possible in future we add a s3://... as an input method in CLI. So I am now marking this as a feature request, although it may not be in a super high spot in our to-do list.

@rayluo rayluo added feature-request A feature should be added or improved. confirmed paramfile emr labels Dec 17, 2015
@fs111
Copy link
Author

fs111 commented Dec 17, 2015

I can see that it isn't a priority, I just stumbled upon it while writing a howto for users of our product and saw the differences. These little paper-cuts tend to confuse users and can be a source of much wasted time. That's why I submitted the issue here.

@sporkthrower
Copy link

sporkthrower commented Jul 13, 2016

While having the console and the cli be consistent and both support http and s3 protocols, the real issue is that users can't currently host a public configuration file in an s3 bucket and make it available for others to use in the console. Since the console requires s3 protocol, people in different regions or accounts will get errors when trying to specify the configuration URI. Using the http protocol is preferred in this case. Related to the following forums post : https://forums.aws.amazon.com/message.jspa?messageID=696248#696248

@fs111
Copy link
Author

fs111 commented Jul 13, 2016

If http is not an option, it should at least behave the same way that EMR bootstrap-actions behave. They can be used from any public bucket, which makes sharing them very easy.

@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
Copy link
Member

jamesls commented Apr 6, 2018

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

@jamesls jamesls reopened this Apr 6, 2018
thoward-godaddy pushed a commit to thoward-godaddy/aws-cli that referenced this issue Feb 12, 2022
Addresses several issues around IDE init as well as Windows init. With this change, the `sam init` command will clone the app templates repo automatically (with shell notifications), and uses a two-step update process so that the existing app templates copy on a user's machine is not deleted unless we have already successfully downloaded a replacement.
@tim-finnigan tim-finnigan self-assigned this Nov 1, 2022
@tim-finnigan
Copy link
Contributor

Checking in as this issue hasn't been active in a while. According to this page in the EMR documentation it is now possible to set a s3:// path for the configuration file. Does that address the original feature request? Please let us know if there's anything you wanted to expand on or clarify here. Thanks!

@tim-finnigan tim-finnigan added response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. p3 This is a minor priority issue labels Nov 1, 2022
@fs111
Copy link
Author

fs111 commented Nov 1, 2022

I have not used EMR in many years. Feel free to close this bug.

@github-actions
Copy link

github-actions bot commented Nov 1, 2022

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
emr feature-request A feature should be added or improved. p3 This is a minor priority issue paramfile response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.
Projects
None yet
Development

No branches or pull requests

8 participants