Try our new documentation site.
Starting an EC2 instance
Selecting the AMI
Here is the current list of Amazon Machine Images (AMIs). To start an EC2 instance in the AWS Console, just click the link below. You may also use any other AWS tools to start your EC2 instance.
| Region | AMI ID |
|---|---|
| ap-northeast-1 | ami-4de3c62a |
| ap-northeast-2 | ami-f577a49b |
| ap-south-1 | ami-5467143b |
| ap-southeast-1 | ami-ec2a968f |
| ap-southeast-2 | ami-2d38374e |
| eu-central-1 | ami-84b767eb |
| eu-west-1 | ami-73417e15 |
| sa-east-1 | ami-0a3a5966 |
| us-east-1 | ami-4011aa56 |
| us-east-2 | ami-5cedc939 |
| us-west-1 | ami-74edb614 |
| us-west-2 | ami-6249dd02 |
Note: These AMI IDs may change without notice. You should not hard-code a Gurobi Cloud AMI ID into a program. Instead, your program should always retrieve the list of current AMI IDs from http://packages.gurobi.com/ami.json, which is encoded as a JSON object.
Configuring and Connecting to a Compute Server
Configuring the Inbound Security Group
| Port Range | Protocol | Required | Description |
|---|---|---|---|
| 61000-65000 | TCP | Yes | Compute Server |
| 80 | TCP | No | Web administration |
Note: The source address for the inbound ports should be the computers that will be the clients of the compute server.
Configuration Parameters
Configuration parameters are passed to the instance via EC2 User Data. Each should be formatted as KEY=VALUE, one per line. The following table indicates required and recommended configuration parameters; you can find additional configuration parameters in the Gurobi Remote Services Parameters in the Gurobi Optimizer Reference Manual.
| Key | Description | Required | Comments |
|---|---|---|---|
| CLOUDKEY | The cloud key for your cloud license | Yes | Find this value under the Downloads > Licenses menu on the Gurobi website |
| PASSWORD | The password that the client program must supply in order to submit a job | No | Highly recommended |
| ADMINPASSWORD | The password for performing administrative tasks | No | Highly recommended; for improved security, this should be different from the PASSWORD value |
| IDLESHUTDOWN | If the machine is idle for the specified number of minutes, it will shut down automatically | No | If this is omitted, the machine will not shut down automatically when inactive |
Here is a sample:
CLOUDKEY=d67dcf8a-72b6-11e5-840b-0779f0f8b08e PASSWORD=myAccessPassword ADMINPASSWORD=myAdminPassword IDLESHUTDOWN=60
Connecting to the Instance
For a Gurobi Compute Server, you normally should not login to the server itself. Instead, you should configure a Gurobi Compute Server client to use the Gurobi Compute Server. This is explained in the section "Creating a Compute Server client license" in the Gurobi Optimizer Quick Start Guide. When running an EC2 instance as a Compute Server, you simply need to set COMPUTESERVER to the address of your EC2 instance.
Configuring and Connecting to a Distributed Worker
Configuring the Inbound Security Group
| Port Range | Protocol | Required | Description |
|---|---|---|---|
| 61000-65000 | TCP | Yes | Communication with master |
| 80 | TCP | No | Web administration |
Note: The source address for ports 61000-65000 should be the computers that will be the master for the distributed algorithms. If the master computer is running in the same AWS availability zone, you should use the private network address.
Configuration Parameters
Configuration parameters are passed to the instance via EC2 User Data. Each should be formatted as KEY=VALUE, one per line. The following table indicates required and recommended configuration parameters; you can find additional configuration parameters in the Gurobi Remote Services Parameters section of the Gurobi Optimizer Reference Manual.
| Key | Description | Required | Comments |
|---|---|---|---|
| PASSWORD | The password that the client program must supply in order to submit a job | No | If the worker will be used with another compute server, this should be the exact same value as the compute server |
| ADMINPASSWORD | The password for performing administrative tasks | No | This should be different from the PASSWORD value, if used. |
| IDLESHUTDOWN | If the machine is idle for the specified number of minutes, it will shut down automatically | No | If this is omitted, the machine will not shut down automatically when inactive |
Here is a sample:
PASSWORD=myAccessPassword ADMINPASSWORD=myAdminPassword IDLESHUTDOWN=60
Connecting to the Instance
For a distributed worker, you normally should not login to the server itself. Instead, you should add the address of the EC2 instance to the WorkerPool parameter when solving a model. Additionally, if you configured the distributed worker with a PASSWORD, you should use that value in the WorkerPassword parameter.
Configuring and Connecting to a Traditional Computer
Configuring the Inbound Security Group
| Port Range | Protocol | Required | Description |
|---|---|---|---|
| 22 | TCP | Yes | ssh access to computer |
Configuration Parameters
Configuration parameters are passed to the instance via EC2 User
Data. The user data should consist of a single line:
CLOUDKEY=value; you can find the cloud key value under the
Downloads > Licenses menu on the Gurobi website.
Connecting to the Instance
The AMI is built on Ubuntu Cloud images
for Amazon EC2. This is a 64-bit system running Ubuntu 14.04. The
initial username is ubuntu, which has sudo privileges. Use
your private key to connect to this account on the server. A Gurobi license
key is installed automatically; no additional Gurobi license is
required.
