Getting started with Scalable Graphics and NVIDIA GRID on AWS

          powered-by-nv-grid

Instructions (updated on February 24th, 2016 for Release version 1.8.0)

If you are looking for the instuctions and clients for the previous release (version 1.3.1), please see below on this page.

On February 12th, 2016, we have released our new Windows Server 2012R2 AMI (Release version 1.8.0) for AWS NVIDIA GRID based GPU instances (i.e. g2.2xlarge and g2.8xlarge instances). New instructions and clients will be posted here shortly. Please come back soon to discover the whole new available features!

For those of you who cannot wait, just dowload the client application for your specific device architecture:

Windows

PC, laptop and Surface Pro

Available

  • Req: Vista, 7, 8, 10+
  • Mouse
  • Keyboard
  • Touch screen
  • Joypads (up to 4)
  • USB sharing
Download

OS X

Apple MacBook and Mac

Available

  • Req: OS X 10+
  • Mouse
  • Keyboard
  • Touch screen
  • Joypads (up to 2)
Download

Linux

Linux PC and device

Coming soon

  • Req:
  • Mouse
  • Keyboard
  • Touch screen
  • Joypad
Contact us

Browser

For desktop web browser

Available

  • Req: Flash Player
  • Mouse
  • Keyboard
  • Touch screen
  • Joypad
Connect now

Android

Tablet and smartphone

Available

  • Req: Android 4.4.2+
  • Mouse
  • Keyboard
  • Touch screen
  • Joypads (up to 2)
Download

iOS

Apple iPod and iPad

Available

  • Req: iOS 8+
  • Mouse
  • Keyboard
  • Touch screen
  • Joypad
Contact us

Instructions (updated on March 30th, 2015 for Release version 1.3.1)

On March 30th, 2015, we have released our new Windows Server 2012R2 AMI (Release version 1.3.1) for AWS NVIDIA GRID based GPU instances (i.e. g2.2xlarge instances). This new release brings a whole set of new features (including file transfer, text copy/paste, server-side video recording, pure http streaming on port 80 to go through Proxies, streaming encryption) as well as many stability, image quality and performance enhancements.

If you are already a user of our previously published AMI, we warmly invite you to switch to this new release. If you did not get the chance to test our CGX middleware, now is the right time to do so. Thanks to the feedback provided by our early adopters, we have taken our solution to another level of functionalities and performance.

This page describes the instructions to launch your Windows Server 2012R2 instance on Amazon Web Services and to connect to it to start steaming your 3D game or application. All you need is:

  • A valid AWS account.
  • A good Internet connection (we recommend at least 3 Mb/s download bandwidth available for 720p resolution, the higher the better).
  • A client device (currently Windows PC, Android device and OSX MacBook/Mac computer; a TestFlight beta version for iOS devices is available on request).

What you get is an instant high performance remote access to the Windows desktop of your instance, with full 3D acceleration and sound suport. Currently supported inputs include: mouse/keyboard, joypad and multi-touch. Other USB devices can also be used with a third-party “USB over IP” software solution.

With this new AMI release, it is now possible for you to create your own AMI based on our AMI. You no longer need to contact us for white listing it. You can even sell your own AMI based on our AMI on the AWS Marketplace.

[/full_width]

Step 1: launch your Windows instance

  1. Sign in with your existing account or create an AWS account at: https://portal.aws.amazon.com/gp/aws/developer/registration/index.html

    Amazon Web Services Sign In

    Amazon Web Services Sign In

     

  2. Open the Amazon EC2 console at: https://console.asw.amazon.com/ec2/

    AWS Management Console

    AWS Management Console

     

  3. From the navigation bar (in the top right corner of the screen), select the region for the instance (preferably the closest location for better latency performance). Today, our AMI is available for GPU instances located in the following regions: US East (Virginia), US West (Oregon), US West (Northern California), EU West (Ireland), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo).

    EC2 Region Selection

    EC2 Region Selection

     

  4. On the EC2 console dashboard, click Launch Instance.

    EC2 Launch Instance

    EC2 Launch Instance

     

  5. The Choose an Amazon Machine Image (AMI) page displays a list of basic configurations called Amazon Machine Images (AMIs) that serve as template for your instance. You need to look for our CGX 3D desktop remoting for Windows Server 2012R2 AMI in the AWS Marketplace section of the page, and then click Select.

    Choose an Amazon Machine Image

    Choose an Amazon Machine Image

    Alternatively, you can directly browse our AMI page on the AWS Markeplace: https://aws.amazon.com/marketplace/pp/B00OPU8HFQ

    CGX 3D desktop remoting for Windows Server 2012

    CGX 3D desktop remoting for Windows Server 2012

  6. On the Choose an Instance Type page, you can select the hardware configuration for your instance. The g2.2xlarge instance type (in the GPU instances family) is the only possible choice and is selected by default, as this is the only instance type supporting NVIDA GRID and our middleware.

    Choose an Instance Type

    Choose an Instance Type

  7. Click Review and Launch to accept the default settings and let the wizard complete the rest of steps for you.

    Review and Launch

    Review and Launch

  8. On the Review Instance Launch page, under Security Groups, you’ll see that the wizard created and selected a security group for you: this security group is configured to allow you to connect later with our client software. On this page, you can also review all the settings of your instance. For now, you can leave all the parameters untouched.
  9. Click Launch.

    Launch Instance

    Launch Instance

  10. In the Select an existing key pair or create a new key pair dialog box, you can select Choose an existing key pair, to select a key you already created. Alternatively, you can create a new key pair. Select Create a new key pair, enter a name for the key pair, and then click Download Key Pair. This is the only chance for you to save the private key file, so be sure to download it. Save the private key file in a safe place. You’ll need to provide the name of your key pair when you launch an instance and the corresponding private key each time you connect to the instance.
    Caution: Don’t select the Proceed without a key pair option. If you launch your instance without a key pair, then you can’t connect to it.
    When you are ready, select the acknowledgment check box, and then click Launch Instances.
  11. A confirmation page lets you know that your instance is launching. Click View Instances to close the confirmation page and return to the console.On the Instances page, you can view the status of the launch. It takes a short time for the instance to launch. When you launch an instance, its initial state is pending. After the instance starts, it state changes to running and it receives a Public DNS Name and a Public IP Address.
  12. Record the public IP address for your instance because you’ll need it for the next step.
  13. For additional information about AWS Microsoft Windows instances, please visit the official documentation: http://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/concepts.html

Step 2: connect to your Windows instance

To connect to the Windows instance, you must retrieve the initial Administrator password and then specify this password when you connect to your instance using one of our client applications.

  1. In the Amazon EC2 console, select the instance.
  2. In the Actions menu, click Get Windows Password (it will take a few minutes after the instance is launched before the password is available).
  3. Click Browse and navigate to the private key file you created when you launched the instance. Select the file and click Open to copy the entire contents of the file into contents box.
  4. Click Decrypt Password. The console displays the default administrator password for the instance. Record the default administrator password. You need this password to connect to the instance.
  5. Get the Public IP of your EC2 instance. This is the only information (with the administrator password) you will need to connect to your instance.

Caution: Never connect to your instance with RDP, as it would break the NVIDIA driver. If you have done this by mistake, proceed with the RDP session, and reboot the instance.

Now, download and install the client application for your specific device architecture:

Windows

PC, laptop and Surface Pro

Available

  • Req: Vista, 7, 8+
  • Mouse
  • Keyboard
  • Touch screen
  • Joypad
Download

Android

Tablet and smartphone

Available

  • Req: Android 4.1+
  • Mouse
  • Keyboard
  • Touch screen
  • Joypad
Download

Tegra

Android Tegra device

Available

  • Req: Android 4.1+
  • Mouse
  • Keyboard
  • Touch screen
  • Joypad
Download

OS X

Apple MacBook and Mac

Available

  • Req: OS X 10
  • Mouse
  • Keyboard
  • Touch screen
  • Joypad
Download

iOS

Apple iPod and iPad

TestFlight Beta

  • Req: iOS 8
  • Mouse
  • Keyboard
  • Touch screen
  • Joypad
Contact us

Other

For unlisted devices

Under dev

  • Targets
  • Linux
  • Windows Phone
  • Windows Metro
  • Web browser
Contact us

Our client application will present a Graphical User Interface to enter the connection information. For instance, the Windows version will look like this:

AWS CGX Client GUI

The GUI may look different on other platforms, but it will require you to enter the same kind of information:

  • IP address: enter the IP address of your EC2 instance
  • Domain: leave empty for now, this field allows to enter a domain for the user
  • User: enter Administrator
  • Password: enter the Administrator password
  • Bitrate: choose the target bitrate, it should be lower to your available download bandwidth (if you are unsure about your available bandwidth, please visit: http://www.speedtest.net to do a bandwidth test)
  • Performance setting: choose to put the emphasis on image quality or on latency
  • Display resolution: choose the display resolution for the remote Windows desktop
  • Disable audio: check to mute sound
  • Use http/port 80: check if you want to use pure http streaming through port 80
  • Bypass proxy detection: check to disable automatic proxy detection, if you are sure you do not use a Proxy; when this is not checked, our software automatically detects Proxy configuration, and tries to connect through port 80
  • Game mode: check if you want to use UDP instead of TCP to reduce latency further
  • AES encryption: check if you want to encrypt the video stream (AES 256 encryption)
  • Record session: check to record your session on the server side; when your session is over, you can download the movie with the Download Last Record button

Finally, click on Connect to connect to your instance.