Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/7596#issuecomment-125673175
That's correct. What I am suggesting is that there is already an adequate
solution to your use case.
Instead of needing 2 separate sets of AWS keys, one to launch the instances
and one for the instances to access S3, you can launch the instances with
one set of AWS keys and assign those instances to an IAM role that lets
them access S3.
In general, using IAM roles will be preferable to using keys, so I think
the solution available to you now is better than the one you are proposing
here.
Adding an additional option does not seem like the best thing to do here.
Makes sense?
2015ë
7ì 28ì¼ (í) ì¤ì 3:34, Jan Zikes
[email protected]>ëì´ ìì±:
> @nchammas <https://github.com/nchammas> you are probably right that you
> can create IAM role and then use this role to access the S3, but you can't
> use this when you have just AWS keys and no IAM role. At least this is how
> I understand how EC2 works.
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/7596#issuecomment-125483602>.
>
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
