That’s more secure than it might look, because the ssh server is configured to only connect by SSH keys, not by username/password.

User names are OS defaults, in this case, ubuntu.

You can use ordinary ssh with the private key you downloaded to access the server.

Take note of the “Public IPv4 DNS” – that’s the name of your new server.

Return to the AWS Console and click on “Running instances” to see the details of your server.

Follow through the instructions to actually launch your machine.

This is a passphrase-free key, so keeping it secure is critical.

Next you will be given the option of supplying an SSH key pair or createing a pair for access to the machine.įollow the instructions to create a new pair and to download a copy of the private key (.

/32 on the end of the IP addresses allows the last 5 bits to vary.Ĭlick “Review and Launch”, then “Launch”.

I used my home IP address and the address of my CS office PC.

This lets you set up firewall rules that restrict access to your machine. Can help ot identify your machines if you have a lot of them.

I raised the drive size to 30Gb, the largest available without extra charge.Īdding tags is optional.

I left everything else on defaults, and clicked “Next: Add Storage”.For a CI runner, I don’t think that would be a major concern. Purportedly, this saves money at the cost of occasional service unavailibility. Our educational accounts are limited to “nano” and “micro” sizes.

How to install gitlab server from awx