[jira] [Commented] (SPARK-3180) Better control of security groups

2014-08-21 Thread Allan Douglas R. de Oliveira (JIRA)

[ 
https://issues.apache.org/jira/browse/SPARK-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14106171#comment-14106171
 ] 

Allan Douglas R. de Oliveira commented on SPARK-3180:
-

PR: https://github.com/apache/spark/pull/2088

 Better control of security groups
 -

 Key: SPARK-3180
 URL: https://issues.apache.org/jira/browse/SPARK-3180
 Project: Spark
  Issue Type: Improvement
Reporter: Allan Douglas R. de Oliveira

 Two features can be combined together to provide better control of security 
 group policies:
 - The ability to specify the address authorized to access the default 
 security group (instead of letting everyone: 0.0.0.0/0)
 - The possibility to place the created machines on a custom security group
 One can use the combinations of the two flags to restrict external access to 
 the provided security group (e.g by setting the authorized address to 
 127.0.0.1/32) while maintaining compatibility with the current behavior.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org



[jira] [Commented] (SPARK-3180) Better control of security groups

2014-08-21 Thread Allan Douglas R. de Oliveira (JIRA)

[ 
https://issues.apache.org/jira/browse/SPARK-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14106177#comment-14106177
 ] 

Allan Douglas R. de Oliveira commented on SPARK-3180:
-

Perhaps it also solves SPARK-2528

 Better control of security groups
 -

 Key: SPARK-3180
 URL: https://issues.apache.org/jira/browse/SPARK-3180
 Project: Spark
  Issue Type: Improvement
Reporter: Allan Douglas R. de Oliveira

 Two features can be combined together to provide better control of security 
 group policies:
 - The ability to specify the address authorized to access the default 
 security group (instead of letting everyone: 0.0.0.0/0)
 - The possibility to place the created machines on a custom security group
 One can use the combinations of the two flags to restrict external access to 
 the provided security group (e.g by setting the authorized address to 
 127.0.0.1/32) while maintaining compatibility with the current behavior.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org



[jira] [Commented] (SPARK-3180) Better control of security groups

2014-08-21 Thread Apache Spark (JIRA)

[ 
https://issues.apache.org/jira/browse/SPARK-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14106176#comment-14106176
 ] 

Apache Spark commented on SPARK-3180:
-

User 'douglaz' has created a pull request for this issue:
https://github.com/apache/spark/pull/2088

 Better control of security groups
 -

 Key: SPARK-3180
 URL: https://issues.apache.org/jira/browse/SPARK-3180
 Project: Spark
  Issue Type: Improvement
Reporter: Allan Douglas R. de Oliveira

 Two features can be combined together to provide better control of security 
 group policies:
 - The ability to specify the address authorized to access the default 
 security group (instead of letting everyone: 0.0.0.0/0)
 - The possibility to place the created machines on a custom security group
 One can use the combinations of the two flags to restrict external access to 
 the provided security group (e.g by setting the authorized address to 
 127.0.0.1/32) while maintaining compatibility with the current behavior.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org