You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Josh Rosen (JIRA)" <ji...@apache.org> on 2015/09/16 20:51:46 UTC
[jira] [Resolved] (SPARK-3949) Use IAMRole in lieu of static access
key-id/secret
[ https://issues.apache.org/jira/browse/SPARK-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Rosen resolved SPARK-3949.
-------------------------------
Resolution: Incomplete
As of SPARK-8576, spark-ec2 can launch instances with IAM instance roles. I'm going to close this issue as "Incomplete" since it's underspecified; it would be helpful to know more specifically where you think we need support for IAM roles instead of keys (i.e. while launching the cluster? for configuring access to S3?).
> Use IAMRole in lieu of static access key-id/secret
> --------------------------------------------------
>
> Key: SPARK-3949
> URL: https://issues.apache.org/jira/browse/SPARK-3949
> Project: Spark
> Issue Type: Improvement
> Components: EC2
> Affects Versions: 1.1.0
> Reporter: Rangarajan Sreenivasan
>
> Spark currently supports AWS resource access through user-specific key-id/secret. While this works, the AWS recommended way is to use IAM Roles instead of specific key-id/secrets.
> http://docs.aws.amazon.com/IAM/latest/UserGuide/IAMBestPractices.html#use-roles-with-ec2
> http://docs.aws.amazon.com/IAM/latest/UserGuide/IAM_Introduction.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org