Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/1120#issuecomment-54866074
There is probably a use case for wanting separate keys to access S3 than
the ones you use to launch EC2 instances, but perhaps it's fine for starters to
have them be the same and open a separate PR in the future to make it possible
for them to be different.
> Also, just to be paranoid, is there any security concern with implicitly
copying the launch credentials to the cluster?
Probably not directly since, as Dan pointed out, I think EMR does the same.
But we do have an existing security problem reported in
[SPARK-2528](https://issues.apache.org/jira/browse/SPARK-2528), which is that
`spark-ec2` opens access to SSH from `0.0.0.0/0` by default.
---
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]
