docs need additional data, re custom AMIs and launch targets

[galaxyproject]

docs need additional data, re custom AMIs and launch targets

[afgane]

You can choose Custom image from the Image dropdown under the advanced options and enter your custom AMI id.
Launching instances into VPC is not supported however. This being an AWS-specific feature, we haven't really even thought about it but if you'd like see about implementing support for it, feel free to issue a pull request.

[MatthewRalston]

@afgane can you confirm that AMI's will launch into a default VPC, however?

[afgane]

Yes. If the account only has VPC access, an instance will get launched into the default VPC. I tested this but let me know if you run into issues.

[MatthewRalston]

Thank you!

[MatthewRalston]

I have another question concerning custom AMIs, cross posted on biostar. Is your ansible playbook the recommended way to build the AMI? Is anything else required? Can I then simply add the image to cloudlaunch?

[afgane]

I posted an answer on the biostar forum and depending on how far you'd like to take the cloud functionality, in addition to the AMI, you are likely going to need the the galaxy and indices file systems. The instructions are available at the link I posted (i.e., https://wiki.galaxyproject.org/CloudMan/Building).