Today, we have been able to use a custom AMI in order to run Rio on many Amazon EC2 instances.

The test we did was quite simple: one instance of our Amazon image (let’s call it server1) ran Rio (rio start all), whereas another instance (let’s call it server2) ran CLI (Rio command-line interface). Multicast being disabled between Amazon EC2 instances, we had to use a Unicast lookup. This can be done in CLI with the following command:
set locators jini://PRIVATE_DNS_NAME_OF_RIO_SERVER_1

We were able to list from server2 the services running on server1. CLI uses the default ServiceDiscoveryManager settings, so when we stop Rio on server1, we had to wait 10 minutes before the services disappeared.

So, do not forget to customize your Rio/Jini environment when using Amazon EC2.

We will soon provide a public AMI, with a customized Rio distribution tuned for Amazon EC2.

Update: there is now a tutorial for running Rio on Amazon EC2 and Rio AMI!

We have written the skeleton pages for the IntelliJ plugins we wrote.

As explained on the right sidebar, this is a fresh new blog whose content is going to be related to the Elastic Grid solution (work in progress) and by extension Amazon EC2, Amazon S3, Amazon SQS, Rio and Jini.

Some interesting screencasts should come soon, so stay tuned!