Return-Path: Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: (qmail 17299 invoked from network); 16 Dec 2009 04:50:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Dec 2009 04:50:45 -0000 Received: (qmail 73349 invoked by uid 500); 16 Dec 2009 04:50:44 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 72950 invoked by uid 500); 16 Dec 2009 04:50:42 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 72729 invoked by uid 99); 16 Dec 2009 04:50:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 04:50:40 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 04:50:39 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 3C1CD234C4A9 for ; Tue, 15 Dec 2009 20:50:18 -0800 (PST) Message-ID: <1169656983.1260939018244.JavaMail.jira@brutus> Date: Wed, 16 Dec 2009 04:50:18 +0000 (UTC) From: "Paul Egan (JIRA)" To: common-dev@hadoop.apache.org Subject: [jira] Created: (HADOOP-6444) Support additional security group option in hadoop-ec2 script MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org 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 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.