You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Brad Willard (JIRA)" <ji...@apache.org> on 2015/05/14 19:07:59 UTC

[jira] [Created] (SPARK-7640) Private VPC with default Spark AMI breaks yum

Brad Willard created SPARK-7640:
-----------------------------------

             Summary: Private VPC with default Spark AMI breaks yum
                 Key: SPARK-7640
                 URL: https://issues.apache.org/jira/browse/SPARK-7640
             Project: Spark
          Issue Type: Improvement
          Components: EC2
    Affects Versions: 1.3.1, 1.3.0
            Reporter: Brad Willard
            Priority: Minor


If you create a spark cluster in a private vpc, the amazon yum repos return 403 permission denied because Amazon cannot discern the vms are in their datacenter. This makes it incredibly annoying to install things like python 2.7 and different compression libs or consider updating anything.

Potential fixes:
Add fedora yum repos on the default ami to ones outside of amazon. 
Change the ami to be based on a non amazon ami, like a standard red-hat one.
Switch everything to support ec2-user like most modern aws amis to make it easier for the user to pick an ami
Petition amazon to open up their repos.

Failed Workaround:
I attempted to use a normal red-hat ami, however the current deploy scripts assume the user and the install path are root. While the deploy script allows you to override the user, they don't work if you set ec2-user basically preventing you from using any current ami other than the default amazon one which is unfortunate.






--
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