GPUBox Web Service is a solution that combines the possibilities of the GPUBox technology and computing power of Amazon's Elastic Compute Cloud (Amazon EC2). It automatically sets up and configures a GPUBox infrastructure on Amazon's instances so multiple-GPU cloud environment can be used in real time in a regular web browser without the need of having any local GPUs.

This document provides information on setting up and managing the GPU cloud environment within GPUBox Web Service. If you need more information about using GPUBox, please refer to the documentation that can be downloaded from Renegatt Software website.

Brief instruction

Step 1:
Acquire license
GPUBox Web Service requires full GPUBox license. License can be purchased on Renegatt Software website.
Step 2:
Launch Amazon AWS instances
Launch the GPU instances on your Amazon AWS account. Choose GPUBox AMI (Amazon Machine Image) to let GPUBox Web Service run correctly.
Follow the instructions from the Preparing environment on Amazon AWS section.
Step 3:
Verify the status
Once all Amazon instances are up and running verify the status of GPUBox infrastructure.
Follow the instructions from the Check the current status of GPUBox infrastructure section.
Step 4:
Your private GPUBox infrastructure is ready!
To use GPUs, you have to connect to just started GPUBox infrastructure. You can do it from one of the available desktop (link is available via GPUBox Web Service status page) or you can start your own instance.
Depends on type of your instance, if it is Windows or Linux you can use command line tool or GPUBox for Windows to allocate and then manage the GPUs.

Preparing environment on Amazon EC2

At first sight this section might seem complex, but it is just described in details. Once you are signed up on Amazon AWS, following the steps from this section will take no more than 10 minutes.

Using GPUBox Web Service on Amazon Elastic Compute Cloud requires an account on Amazon AWS.

Amazon EC2 by default has limit on number of instances that user can run concurrently. The limits must be increased due to operate on greater number of GPUs.

Check the current status of GPUBox infrastructure

Before you start the GPUBox infrastructure on Amazon EC2 you have to check the current status. Click the link that you receive along with the license.

Status of GPUBox infrastructure on Amazon EC2 is not automatically reset. Before you start GPUBox instances, it is important to verify the current status of the service and reset it manually when it is required. After resetting, the status of GPUBox infrastructure must be clear.

If the status is not clear yet, click the Reset status button as follow:

GPU instances on Amazon AWS

Amazon AWS offers three types of instances with access to GPU:
Instance name GPU per instance Generation Networking Performance
g2.2xlarge 1 x GRID K520 Current High
g2.8xlarge 4 x GRID K520 Current 10 Gigabit
cg1.4xlarge 2 x Tesla M2050 Previous 10 Gigabit

The cg1.4xlarge instance type with Tesla GPUs is not accessible from every region. You can read more about previous generation instances on Amazon AWS website

Increasing limits

By default Amazon allows to run 5 instances of a particular type at the same time. To use more than 5 GPUs within GPUBox Web Service you need to increase this limit. Go to the Limits section in the EC2 Management Console. Find the limit that you want to increase, use the Request limit increase link and follow the instructions.

Configuring Security Groups

GPUBox Web Service requires two security rules in order to work properly:
# Type Protocol Range Source
1 All TCP TCP 0 - 65535 <Your IP>
2 All traffic TCP All <Security Group>
The first rule allows your system to configure the instances remotely. The second rule enables the instances to communicate with each other properly.

You can either edit the default security group and use it for your instances or create a new group. Both ways are described in the sections below.

Edit default Security Group (Option 1.)

Log in to your Amazon AWS account and go to the EC2 section.

Open the Security Groups section, select the default Security Group, open the Inbound tab and press the Edit button.

Press the Add Rule button, select the All TCP option as Type and My IP as Source. After that, save the changes with the Save button.

Create new Security Group (Option 2.)

Open the Security Groups section and press the Create Security Group button.

Set your Security gruop name and Description. Press the Add Rule button, select All TCP as Type and My IP as Source. After that, create the Security Group with the Create button.

Once the new Security Group is created you can add the second rule. Select the new Security Group, open the Inbound tab and press the Edit button.

Press the Add Rule button. Select the All traffic option as Type. Now you can either paste the Group ID of your Security Group or start typing its name and select it from the suggestions to fill the Source field automatically. At the end, save the changes by pressing the Save button.

Running and configuring instances

Amazon Machine Image with preconfigured GPUBox is provided by Renegatt Software.

Go to AMI and change the filter to Private images, click right mouse button on the recent GPUBox AMI and select Launch option. Select GPU instances from the list of instance types.

Mark the g2.2xlarge or g2.8xlarge instance type. If you want to use the cg1.4xlarge instances, you need set the generation filter to All generations. Once you choose the instance type, press the Next:Configure Instance Details to move to the next section.

Enter the Number of instances you want to launch. Select the New placement group option and enter the name of your new placement group. At this step you can optionally decide to request Spot Instances. There is no need to change anything in sections 4. Add Storage and 5. Tag Instance, so you can move to the 6. Configure Security Groups section.

It is extremely important to copy and then paste your license into User data in Advanced details section while you create instance.
The license format is exactly the same as for OServer configuration file.

Additionally you can provide option oserver_license_operation="save" to save the license onto the disk , however the image must be recreated afterward to preserve the setup. Next start of the new created AMI will not require to enter the license details.

Choose the Select an existing security group option. Select the Security Group that you have configured before (in the Configuring Security Groups section). At the end, press the Review and Launch button.

You can review the configuration summary for your instances before pressing the Launch button.

On the pop-up window select the Create a new key pair option and enter Key pair name. Then download your *.pem file by pressing the Download Key Pair option. Check the option "I acknowledge that I have access to the selected private key file (gpubox-key.pem), and that without this file, I won't be able to log into my instance." abd end use the Launch Instances button.

Once your instances are launched, your GPUBox infrastructure is ready to use. To verify if all components are up and running you have to check the service status via the link you received in email.

Your instances will be ready to use then the 2/2 checks passed status appears in the Status Checks column.
GPUBox Web Service will not work on the instances in the Initializing... status!

End User License Agreement

GPUBox - Web Service Edition
Copyright © Renegatt Software 2011-2016


IMPORTANT: By downloading, installing or using the "GPUBox - Web Service Edition" Software you (the individual or legal entity) agree to be bound by the terms of this End User License Agreement ("EULA"). If you do not agree to the terms of this EULA you must not download, install or use the Software.

1.1. "License" means a license granted under Section 2.1.
1.2. "License Key" means a serial number that enables You to use the Software.
1.3. "License Type" means the type of License applicable to the Software, as more fully described in the Order.
1.4. "Order" means a purchase order, license agreement or other ordering document issued by You to Renegatt that references this EULA and is accepted by Renegatt as set forth in Section 4.
1.5. "Software" means GPUBox - Web Service Edition computer program.
1.6. "Renegatt" means Renegatt Software company.
1.7. "Device" means Graphics Processing Unit (GPU) compatible with the Software.
1.8. "GPUHours" means billing unit for using the Software. It is an equivalent of using the Software on one Device for one hour. One GPUHour is consumed for every begun hour of using one Device.

2.1. Subject to the terms and conditions of this EULA, Renegatt grants you a non-exclusive, non-transferable License to use the Software in executable code form only in accordance with the License Type for the time resulting from number of obtained GPUHours for which You have paid the applicable fees.
2.2. You may make one copy of the Software for archival purposes only. The copy shall be kept within your possession or control; include all titles, trademarks, copyright and restricted rights notices. You may not otherwise copy the Software without prior written consent granted to You by Renegatt.
2.3. You may run OServer component of the Software on single machine (or virtual machine) only at a time.

3. RESTRICTIONS: You acknowledge that the Software, its structure, organization and source code constitute valuable trade secrets of Renegatt. Accordingly, except as expressly permitted in Section 2 or as otherwise authorized by Renegatt in writing, You will not and will not permit to third party to:
3.1. Sell, lease, license, distribute, sublicense or otherwise transfer in whole or in part the Software to any third party
3.2. Decompile, disassemble, reverse engineer or otherwise attempt to derive source code and algorithms from the Software in whole or in part
3.3. Copy the Software except for archival purposes
3.4. Create, develop, license, install, use or deploy any software or services to circumvent, enable, modify or provide access, permissions or rights which violate the technical restrictions of the Software as described in this EULA. Translate, modify or create derivative works based upon the Software
3.5. Remove any product identification, proprietary, copyright or other notices contained in the Software.

4. ORDER:Your Order is subject to this EULA. No Orders are binding on Renegatt until accepted by Renegatt. Orders for Software are deemed to be accepted upon Renegatt's delivery of the Software included in such Order. Orders issued to Renegatt do not have to be signed to be valid and enforceable.

5. OWNERSHIP: The Software, all copies and portions thereof; improvements, enhancements, modifications and derivative works thereof; and all Intellectual Property Rights therein, are and shall remain the sole and exclusive property of Renegatt. Your rights to use the Software shall be limited to those expressly granted in this EULA. No other rights will respect to the Software or any related Intellectual Property Rights are implied.

6. DISCLAIMER OF WARRANTIES: Renegatt does not warrant that the Software will operate uninterrupted or that the Software or any related website or network access point are free of malicious software and alike or other defects, or that the Software will meet (or is designed to meet) your business requirements. If your use of the Software results in the need to service or replace hardware, software, infrastructure or data, Renegatt is not responsible for any of those costs. The Software is provided on an "as-is" basis without any warranties of any kind. To the maximum extent mandated by law, Renegatt disclaims all warranties, whether expressed, implied or statutory, including any implied warranties of merchantability and fitness for a particular purpose, title, non-infringement and that warranties arising during the course of any business dealings or concerning performance issues regarding or relating to the Software, documentation or any materials furnished or provided to You under this EULA.

7. LIMITATION OF LIABILITY: To the maximum extent mandated by law, in no event will Renegatt be liable for any lost profits or business opportunities, loss of use, loss of revenue, loss of goodwill, business interruption, loss of data or any other indirect, special, incidental or consequential damages under any theory of liability, whether based in contract, tort, negligence, product liability or otherwise.

8.1. Renegatt may terminate this EULA in its entirety effective immediately upon written notice to You if You (a) breach any provision specified in Section 3 and Section 2, (b) fail to pay any portion of the fees under an applicable order within ten (10) days after receiving written notice from Renegatt that payment is past due, (c) breach any other provision of this EULA or (d) you commit a material breach that cannot be rectified.
8.2. If Renegatt terminates this EULA: (a) all Licensed rights to the Software granted to You under this EULA will immediately cease to exist and (b) You must promptly discontinue to use the Software and destroy all copies of the Software and certify in writing to Renegatt that You have fully complied with these requirements.

9.1. Parts of the Software are provided under separate licenses which are specified in "" file.
9.2. "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. ("

10. DATA PRIVACY: You agree that Renegatt may process technical and related information about Your use of the Software which may include network address, hardware identification, operating system, application software, peripheral hardware and non-personally identifiable Software usage statistics to facilitate the provisioning of updates, support or online services.

11.1. Notices: Any notice delivered by Renegatt to You under this EULA will be delivered via mail, email, or fax.
11.2. Severability: If any provision of this EULA is held to be illegal, invalid or unenforceable, the provision will be enforced to the maximum extent permissible so as to effect the intent of the parties and the remaining provisions of this EULA will remain in full force and effect.
11.3. Construction: The headings of the sections of this EULA are for convenience and are not to be used in interpreting this EULA.
11.4. This EULA may be amended only in writing signed by the authorized representatives of both parties.
11.5. Contact Information:

*** END OF EULA ***