We actually have galaxy running within a VPC now. The problem we're running into is that when ec2 instances get created they don't have an I_am profile attached to them so they can't get access to S3 resources. This should just be a parameter past to AWS when the instances get created to attach the Iam profile. I just need to know where the code for creating ec2 instances is and I can test it out.

Please excuse any typos -- Sent from my iPhone

> On Mar 15, 2016, at 10:46 PM, Chris Dagdigian <dag@bioteam.net> wrote:
>
>
> Hi Ryan,
>
> I've never been able to get cloudman to function within a private VPC so if this is your architecture as well and you manage to make progress I'd be interested in learning your methods. Thanks!
>
> Regards,
> Chris
>
>
> Enis Afgan wrote:
>> Hi Ryan,
>> I'm not sure I really understand your question but CloudMan can run under an IAM account - it is just necessary to give the IAM user permissions to create EC2 and S3 resources. Let us know if that's not what you had in mind or if you have any more questions.
>>
>> Cheers,
>> Enis
>
___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
  https://lists.galaxyproject.org/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/