You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Paul Egan (JIRA)" <ji...@apache.org> on 2009/12/16 05:52:18 UTC
[jira] Updated: (HADOOP-6444) Support additional security group
option in hadoop-ec2 script
[ https://issues.apache.org/jira/browse/HADOOP-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Egan updated HADOOP-6444:
------------------------------
Attachment: hadoop-ec2-py-0.3.0.patch
Patch against [cloudera-for-hadoop-on-ec2-py-0.3.0-beta.tar.gz|http://cloudera-packages.s3.amazonaws.com/cloudera-for-hadoop-on-ec2-py-0.3.0-beta.tar.gz] adding a {{security-group}} option.
> Support additional security group option in hadoop-ec2 script
> -------------------------------------------------------------
>
> Key: HADOOP-6444
> URL: https://issues.apache.org/jira/browse/HADOOP-6444
> Project: Hadoop Common
> Issue Type: Improvement
> Components: contrib/ec2
> Reporter: Paul Egan
> Priority: Minor
> Attachments: hadoop-ec2-py-0.3.0.patch
>
>
> When deploying a hadoop cluster on ec2 alongside other services it is very useful to be able to specify additional (pre-existing) security groups to facilitate access control. For example one could use this feature to add a cluster to a generic "hadoop" group, which authorizes hdfs access from instances outside the cluster. Without such an option the access control for the security groups created by the script need to manually updated after cluster launch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.