I've made the AMI public. It's ami-f695f39f and it's called khi.crux3.0.x86_64 

You will need to run it using a paravirtualized boot kernel which allows you to run the custom kernel. Using the ec2 command line tools the command would look like 

ec2-run-instances -z us-east-1c -n 1 -t t1.micro -k ec2-keypair --kernel aki-b4aa75dd ami-f695f39f

Note in particular the kernel you will need to 'preboot' with aki-b4aa75dd 

Just replace the availability zone, instance size and ec2-keypair you want with your own preferences. Login as root with the same ssh-keypair you specified. It's ssh-key login only. Anyway if you use ec2 it's all pretty standard apart from kernel you need to initially boot with. 

Chris K.

On Mon, Apr 15, 2013 at 3:52 PM, James Mills <prologic@shortcircuit.net.au> wrote:

I am. I also have and operate OpenVZ images if anyone is interested in these?

cheers
James

Sent from my iPad

On 15/04/2013, at 17:50, Chris Kruger <chris.kruger@gmail.com> wrote:

> Hi Folks,
>
> I don't know if anybody here uses Amazon's EC2, but maybe some here will be interested.
>
> I've always wanted to run CRUX in the cloud so I built an Amazon AMI (Amazon Machine Image) to allow me to do so.
>
> If anybody else is interested let me know and I can share the AMI with you.
>
> Chris K.

> _______________________________________________
> CRUX mailing list
> CRUX@lists.crux.nu
> http://lists.crux.nu/mailman/listinfo/crux