Update:[05/03/2012] New versions of the LabKey Server AMIs have been released. See Install LabKey in the Cloud for the list of available AMIs and for instructions on using one.
With the release of LabKey Server v11.3, we will start publishing a Amazon Web Services AMI for every LabKey server release. So if you have an Amazon Web Services account, then with just a few clicks you can bring up LabKey Server and get working.
Amazon EC2 Published Images
| Region |
arch |
ami |
Description |
| US West (Oregon) |
amd64 |
ami-dab439ea
|
LabKey Server 11.3(18455) x86-64. Configured to work on instances with 8GB of memory or more (m1.large or larger). Operating System = Ubuntu 11.10
|
| US West (Oregon) |
i386 |
ami-deb439ee
|
LabKey Server 11.3(18455) 32bit. Configured to work on instances with 2GB of memory or more (m1.small or larger). Operating System = Ubuntu 11.10
|
| US East |
amd64 |
ami-c1489ca8
|
LabKey Server 11.3(18455) x86-64. Configured to work on instances with 8GB of memory or more (m1.large or larger). Operating System = Ubuntu 11.10
|
| US East |
i386 |
ami-ab489cc2
|
LabKey Server 11.3(18455) 32bit. Configured to work on instances with 2GB of memory or more (m1.small or larger). Operating System = Ubuntu 11.10
|
How to Get Started with the AMI
Using the Management Console
If you use the AWS Management Console to start and stop your AWS instances then all you need to do is
- click on the link in the ami column, above, for the AMI you would like to start
- This will open the AWS Management Console so you can login
- Start a new instance using the AMI
Once the instance is started, all you need to do is open your favorite browser and connect to the new instance. You will be asked to initialize your LabKey Server and you should be ready to go.
NOTE: By default the AMI will have only 8GB of storage available when you start it. This can be changed at start time or at a later date.
Using the command line
If you prefer to use the command line, all you need to do is run
ec2-run-instances <ami-id> -k <EC2_KEYPAIR> -t <instance-type> --region <region-name>
where <region-name> will need to match the AMI you selected above
Once the instance is started, all you need to do is open your favorite browser and connect to the new instance. You will be asked to initialize your LabKey Server and you should be ready to go.
NOTE: By default the AMI will have only 8GB of storage available when you start it. This can be changed at start time or at a later date.
This is sort of geeky information, but I thought I would add it here just in case anyone was interested. The LabKey Server uses a number of other open source packages. Information about the LabKey Server and the other software is below.
NOTE: This information is for advanced users, most people do not need to read any farther
Start and Stop your LabKey Server
Log on to your instance using ssh and then run
To Start the Server
sudo /etc/init.d/tomcat start
To Stop the Server
sudo /etc/init.d/tomcat stop
How to connect to the instance using SSH
You will need to connect to the server public/private keypair authentication
- Username = ubuntu
- Keypair that you selected when started the instance.
You can use a command similar to
ssh -i ~/ec2/id_rsa_keypairName ubuntu@INSTANCE_IP
Logins as the root user is disabled by default, so to become the root user you will need to use the sudo command. Similar to
Tomcat
- Version: 6.0.33
- Installation Directory:
/labkey/apps/tomcat
- Log Directory:
/labkey/apps/tomcat/logs
- Service Script:
/etc/init.d/tomcat
PostgreSQL
- Version: 9.0.5
- Installation Directory:
/labkey/apps/postgresql-9.0.5
- Data Directory:
/labkey/apps/postgresql-9.0.5/data
- Log Directory:
/labkey/apps/postgresql-9.0.5/data/pg_log
Update 1: LabKey has released an important security update for LabKey Server v11.3. I strongly recommend downloading the update and upgrading your new instance immediately after installation. You can find the update here. You can find instructions for upgrading your new LabKey Server at labkey.org.
Update 2: The LabKey Server AMI will not run on the t1.micro instance due to the limited resources of this instance type.
Share this: