Get Started

Get started with the Intel Developer Cloud console. In this guide, you learn how to:

Sign Up

Sign up with your corporate email address at Intel® Developer Cloud Console.

1. Enter your email ID and click on the Sign In button.

2. Keep the email field empty and just click on the “Employee Sign in”

Intel Developer Cloud Console Sign-In

Set Up SSH Keys

Setting up SSH Keys is a one-time task. See also SSH Keys.

Warning

Never share your private keys with anyone. Never create a SSH Private key without a passphrase.

Generate an SSH Key

Select the tab below per your operating system (OS).

Linux* OSWindows PowerShell

1. Launch a Terminal on your local system.

2. Copy and paste the following to your terminal to generate SSH Keys

   ssh-keygen -t rsa -b 4096 -f ~/.ssh/id_rsa
   

3. If you are prompted to overwrite, select No.

4. Copy and paste the following to your terminal to open your SSH key:

   vi ~/.ssh/id_rsa.pub
   

5. Upload the generated file.

Upload an SSH Key

1. Once signed in to the console, click on the keys menu.

   

   Cloud Console Keys Menu

2. At the keys screen, click on upload key button.

3. Specify a name for your key and paste the contents of your key on the key contents field. To generate a key, follow Generate an SSH Key.

   

   Create name for SSH key

4. The uploaded key will appear in the keys screen. You can delete a key. To rename a key, you must delete the original key and upload a new one with a new name.

   

   Keys - Account Keys

Access from Corporate Network

Warning

If you are connecting to Intel Developer Cloud from your company Corporate Network, you will need to update SSH config file.

Note

If you connect using PowerShell on Microsoft Windows Operating System, you must install gitforwindows.

1. Setting up SSH Configuration is an one-time task.

2. Your SSH configuration file is in a folder named .ssh under your user’s home folder. If the file is not present, create one.

3. Open the .ssh/config file with an editor:

   ~/.ssh/config
   

4. Copy and paste the following configuration to .ssh/config, per your Operating System.

   Linux* OSWindows PowerShell

   Host 146.152.*.*
   ProxyCommand /usr/bin/nc -x PROXYSERVER:PROXYSPORT %h %p
   

5. From your Lab Administrator, get PROXYSERVER and PROXYPORT in your Corporate Network for SSH, NOT for HTTP/HTTPS Proxy.

6. Replace PROXYSERVER and PROXYPORT with the information you received from your lab administrator and save the SSH Config file.

Add a cloud credit coupon

1. Open the cloud credits option from your account menu.

   

   Cloud Credits

2. Click on the Redeem coupon button.

   

   Redeem Coupon Button

3. Provide a coupon code.

4. Cick on Redeem.

Note

The system will validate the code. Once it is accepted it will show up under the detailed list of credit information (due to latency, the code can appear in the list after a few minutes).

Launch a compute instance

There are two ways to launch a compute instance.

Launch a compute instance

Launch from Homepage Catalog

1. Select one of the product families available in the homepage.

2. At the Launch Instance page select your instance type, specify a name, select a machine operating system, and select the SSH keys that will work with the instance.

3. Click Launch.

Accessing a compute instance

To access your instance with an SSH client:

Linux* OSWindows PowerShell

1. From the Intel network:

   To connect to the Developer Cloud tenant SSH proxy, you need to configure the SSH client to use the Intel SOCKS proxy. You can do this by adding the following configuration to ~/.ssh/config.

   Host 146.152.*.*
   
   ProxyCommand /usr/bin/nc -x proxy-dmz.intel.com:1080 %h %p
   

2. Open an SSH client.

3. Locate your SSH key file (my-key.ssh). The wizard automatically detects the key you used to launch the instance.

4. Your key must not be publicly visible for SSH to work. Use this command:

   chmod 400 my-key.ssh
   

5. SSH command to connect to instance:

   ssh -J guest-dev8@10.165.57.246 ubuntu@172.16.1.118
   

Please note that in most cases the username above will be correct, however please ensure that you read your instance usage instructions to ensure that the instance owner has not changed the default instance use