[
https://issues.apache.org/jira/browse/SPARK-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272601#comment-14272601
]
Nicholas Chammas commented on SPARK-1532:
-----------------------------------------
I believe this capability is now present (at least in {{master}}) under the
following option:
{code}
--authorized-address=AUTHORIZED_ADDRESS
Address to authorize on created security groups
(default: 0.0.0.0/0)
{code}
[~foundart] - Can you confirm this solves your problem?
> provide option for more restrictive firewall rule in ec2/spark_ec2.py
> ---------------------------------------------------------------------
>
> Key: SPARK-1532
> URL: https://issues.apache.org/jira/browse/SPARK-1532
> Project: Spark
> Issue Type: Improvement
> Components: EC2
> Affects Versions: 0.9.0
> Reporter: Art Peel
> Priority: Minor
>
> When ec2/spark_ec2.py sets up firewall rules for various ports, it uses an
> extremely lenient hard-coded value for allowed IP addresses: '0.0.0.0/0'
> It would be very useful for deployments to allow specifying the allowed IP
> addresses as a command-line option to ec2/spark_ec2.py. This new
> configuration parameter should have as its default the current hard-coded
> value, '0.0.0.0/0', so the functionality of ec2/spark_ec2.py will change only
> for those users who specify the new option.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
