Launch an Ubuntu machine on AWS

Spinning up an EC2 instance

  1. Log into AWS and go to the EC2 dashboard; Click “Launch Instance”

https://secoda.intercom-attachments-1.com/i/o/335306855/06af3027a4ae54aa3b979b5a/c312989-0gtf9PBQ.png?expires=1620869410&signature=49ccd08852ba967b984ddae0546c46ca7cede56635489023b6766c600364726c

  1. Select Ubuntu 20.04

  2. Select the instance type. You should choose at least t2.large as we need at least 8GB of RAM.

  3. Make sure you select the VPC that also includes the data sources you will want to connect to.

https://secoda.intercom-attachments-1.com/i/o/335306857/14432eb5a7ecd2bbf695d342/aa062f9-Y2WrzG1f.png?expires=1620869410&signature=253af4d0ff9481181c132bf7f0f060dec8144511240ecd2cbeb49f1813955616

  1. Make sure there is at least 64 GB of storage. This can fluctuate depending on the number of resources a company has

  2. Optionally add some Tags, e.g. app = secoda. In general, you can skip this unless you have a lot of instances.

  3. Set the security groups.

Inbound rules

We need to open ports 80 (http) and 443 (https) so that you can connect to the server from a browser, as well as port 22 (ssh) so that we can ssh into the instance to configure it and run Secoda. If you're running behind a VPN you can specify the VPN's IP address in the Source column.

https://secoda.intercom-attachments-1.com/i/o/335306858/695e17f7a6a660b69c705fe2/045cf8d-Q4vl96eg.png?expires=1620869410&signature=ae38fd060665ff9b6907f56ba06e6b0825b67583777b38655df52dc76d9ca38c

Outbound rules

Please have all outbound traffic set for the security group. This allows us to track how users are using the application for support and product improvement purposes. If you are not able to allow all outbound traffic please let us know.

  1. When launching the instance, create a new key pair or select a preexisting one. Download the .pem file and make sure it’s stored in a folder you’ll remember on your computer

https://secoda.intercom-attachments-1.com/i/o/335306859/de7ddcc22213eec8b34cc5a0/e3167f9--r4LllDy.png?expires=1620869410&signature=ab966bc78bea9c3fc69d8b22f09c5bea0864d0bbe763035672a0a858bfc625a5

  1. After a few minutes you should see the instance with a status of running

Connect to the EC2 instance