[Seaside] Seaside on EC2 Amazon Service

[Nick Ager]

Hi Larry,

Norbert is working on a set of Chef [1] recipes for automating the creating
of cloud images. These Chef recipes will supersedes the AMI I created, which
was difficult to maintain and parameterise for different uses.

However in the meantime it seems like you're having a problem just getting
started on EC2, prior to any Seaside specific configuration. Thing to check
are:

1) Make sure you are ssh ing with a specified user, this varies depending on
distribution. For Amazon's Linux distribution the user is ec2-user so you
log-in with:
    ssh ec2-user at ec2-79-125-71-160.eu-west-1.compute.amazonaws.com
 For Ubuntu IIRC you have to login as root

2) Ensure you have have enabled SSH in your firewall configuration - though
it doesn't sound as though that's your problem as the connection isn't
timing-out, but failing during authenticating. SSH has a verbose options
(-v) which can help diagnose where the problem lies:
    ssh -v  ec2-user at ec2-79-125-71-160.eu-west-1.compute.amazonaws.com

3) I know of three ways of using keys to authenticate with EC2 instances
(there may be more). The method I describe in the blog post [2] makes use of
"Cloud-init" [3] which is preinstalled for Amazon's Linux distribution -
Cloud-init might not be installed with other distributions. Make sure you
follow the syntax I describe in the post:

#cloud-config
ssh_authorized_keys:
  - ssh-rsa
AAAAB3NzaC1AAAABIwAAAQEAz21r7532bmknElW8cZhECXFqf/Z/+VRFSy........BtxwC2offQ==nickager at nicksmac.local

Make sure you include the " - " before your key and lines "#cloud-config" &
"ssh_authorized_keys:"
I find it helpful to form the syntax in a text editor prior to posting into
the web-form.

It's most probable that this key step is failing for you. I've just tested
again the instructions and they still work for me. However, as I mentioned
above there are other ways to pass keys to Amazon - see [4] [5] - though you
might have to install ec2 tools [6].

For whatever reason it seems Amazon doesn't have the keys it needs to
authenticate you on the instance you've created. You should terminate that
instance and start again. Don't worry about creating and terminating lots of
instances while you experiment with the cloud.

Final thought make sure you are ssh ing using the public DNS address NOT the
private DNS address that Amazon also displays.

Hope this helps

Nick

[1] http://wiki.opscode.com/display/chef/Home
[2]
http://www.nickager.com/blog/Installing-Gemstone-on-an-Amazon-EC2-Linux-instance
[3] https://help.ubuntu.com/community/CloudInit
[4]
http://www.robertsosinski.com/2008/01/26/starting-amazon-ec2-with-mac-os-x/
[5] http://alestic.com/2010/10/ec2-ssh-keys
[6]
http://www.dougjaworski.com/blog/how-to-install-amazon-ec2-tools-on-a-mac/





On 11 October 2011 20:03, Lawrence Kellogg <mac.hive at me.com> wrote:

> Hello,
>  Does anybody have a good shortcut for getting an Seaside/Gemstone EC2 AMI
> up and running
> on Amazon so I can try out a Seaside application? I tried Nick Ager's
> instructions
> but the AMI files are no longer around.
>
>  Thanks,
>
>  Larry
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20111012/76a6ed9f/attachment.htm