From 7957a00ddfd7df9108d84f98f9dcb276851b68f8 Mon Sep 17 00:00:00 2001 From: pvtroshin Date: Fri, 9 Dec 2011 17:23:23 +0000 Subject: [PATCH] AMI ID update git-svn-id: link to svn.lifesci.dundee.ac.uk/svn/barton/ptroshin/JABA2@4809 e3abac25-378b-4346-85de-24260fe3988d --- website/man_awscloud.html | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/website/man_awscloud.html b/website/man_awscloud.html index 21cd30c..638cd51 100644 --- a/website/man_awscloud.html +++ b/website/man_awscloud.html @@ -10,11 +10,6 @@ -
@@ -69,7 +64,7 @@
  • your organization already uses the Amazon cloud and you do not want to do any special arrangements for the JABAWS
  • you want to benefit from the Amazon automatic scaling and monitoring to make sure JABAWS is always ready
    • -

    If you know what to do than JABAWS AMI ID is ami-40fecd34, manifest 846107356395/JABAWS2 to get you started, if not please refer to How to use JABAWS on the Amazon EC2 cloud pages.

    +

    If you know what to do than JABAWS AMI ID is ami-d1d5e9a5, manifest 846107356395/JABAWS 2 to get you started, if not please refer to How to use JABAWS on the Amazon EC2 cloud pages.

    Alternatively you can use JABAWS on the Amazon Elastic BeanStalk. You may want to use this option to deploy JABAWS in the cluster configuration.

    -- 1.7.10.2