Maybe I misunderstand what you're trying to do, but you shouldn't have to
use ssh-add or anything of the sort; cloudlaunch will do this for you.
When you put your credentials into those two boxes at
usegalaxy.org/cloudlaunch, what exactly happens?
On Tue, Oct 29, 2013 at 11:21 AM, Manisha Sapre <msa...@nmdp.org> wrote:
> Yes , all users have been allotted a private key , this error is after
> ssh-add ( private key),
> From: Dannon Baker <dannon.ba...@gmail.com>
> Date: Tuesday, October 29, 2013 10:15 AM
> To: System Administrator <msa...@nmdp.org>
> Cc: "email@example.com" <firstname.lastname@example.org>, David
> Roe <d...@nmdp.org>
> Subject: Re: [galaxy-dev] cloning Galaxy cluster on cloud Amazon EC2
> Whoever your organization administrator is will need to either create
> those keys for you, or allow your IAM user access to them. Are you able to
> contact the person that administers your account?
> On Tue, Oct 29, 2013 at 10:52 AM, Manisha Sapre <msa...@nmdp.org> wrote:
> Good Morning Dannon
>> we have paid amazon service, I log into EC2 using organization
>> credentials, but get that screen ( below) while trying to identify account
>> text string in AWS console section
>> Launching a cloud instance of galaxy would require this account text
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:
To search Galaxy mailing lists use the unified search at: