Step 2. Configure and Launch the Instance

The next step is to launch the Instance. Make sure you have your License Key, then return to the EC2 Console.

If you need help getting your License Key, take a look at our article here:

Choose a Plan & Retrieve your License Key

1. Once back in the EC2 Console, choose your Instance Type.

Note:

For the purposes of this tutorial I will be using the t2.micro, but remote.it will work with any general purpose Instance Type. If you have a special Instance Type, please contact our support team and we may be able to assist you.

2. Click Next: Configure Instance Details located in the bottom right.

3. Next to Network, select the VPC that has the Instance you want to make accessible using remote.it. Depending on your configuration, the Network you pick may be different than the default. If your VPC does not have a public subnet available, you will need to select "Auto Assign Public IP".

4. Select a public Subnet. remote.it requires a public IP address with an internet gateway in order to function.

subnet.PNG

5. Scroll down to the bottom of the page and paste your License Key into the "User data" field. Leave the rest of the Advanced Details at their default values.

Advanced_Details.PNG

6. Click Next: Add Storage. You don't have to add any additional storage besides the defaults.

7. Click Next: Add Tags. Give your Instance a simple Name tag so you can keep track of it.

ami_15.PNG

8. Click Next: Configure Security Group.

9. Remove the default Security Group rule.

Note:

The Security Group is what permits you to open ports to allow access to an Instance. By default, AWS has added a rule stating that port 29998 is open. However, remote.it does not require any open ports, so you can delete the rule. AWS will display a warning telling you that the AMI requires port 22 to be open in order to have access, but with remote.it that is not the case.

ami_18.PNG

10. Click the blue Review and Launch button. Make sure your settings are to your liking, then launch your Instance.

Warning:

Make sure to download your Key Pair or use an existing one. The key's .pem file can only be downloaded once and should be saved somewhere secure, as the EC2 Instance requires it for SSH Connections. Also confirm that you have the .pem key for any Instance you are jumping to.

After a few minutes your Instance will come online and become registered to your remote.it account. You can see your Instance under the Instances tab at the EC2 Console. Before moving on to the next step, make sure that the “Instance State” changes from “Pending” to “Running”.  Additionally, make sure that under the “Status check” column, a green check mark appears. This may take a few minutes and you may need to refresh the page.

ami_16.PNG

 

Next, you are going to need to ensure that your remote.it Instance can access the Instance you want to access. There are many ways to do this, but the steps below detail just one method:

11. Clear the filter to see all of the Instances in the region. 

12. Locate the Instance you wish to enable access to using remote.it. Make sure this Instance has the default Security Group added.

Note: Even if the Instance is in a private subnet and is undiscoverable on the internet, it can still be accessed using remote.it. To do this, we must add the default Security group to the target Instance and the remote.it Instance.

13. Click the checkbox next to the remote.it Instance.

14. Open the Actions dropdown menu and find Security.

15. Select Change security groups.

ami_security_group.PNG

16. Under Associated security groups, click on the search bar to get a list of options.

17. Select the default Security Group and click Add security group.

18. Click Save and refresh the page.

The default Security Group has now been added to the remote.it Instance, and connections can now be made.

Now it's time to locate your newly created Instance in the remote.it Desktop App.

Was this article helpful?
0 out of 0 found this helpful