Yes , all users have been allotted a private key , this error is after ssh-add 
( private key),

From: Dannon Baker <dannon.ba...@gmail.com<mailto:dannon.ba...@gmail.com>>
Date: Tuesday, October 29, 2013 10:15 AM
To: System Administrator <msa...@nmdp.org<mailto:msa...@nmdp.org>>
Cc: "galaxy-dev@lists.bx.psu.edu<mailto:galaxy-dev@lists.bx.psu.edu>" 
<galaxy-dev@lists.bx.psu.edu<mailto:galaxy-dev@lists.bx.psu.edu>>, David Roe 
<d...@nmdp.org<mailto: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<mailto: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 string

___________________________________________________________
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:
  http://lists.bx.psu.edu/

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

Reply via email to