AWS Setup Guide - nearform/nscale GitHub Wiki

Requirements

Instantiating nscale-base AMI

We can use the nscale-base AMI "bookmark" to get started. This public AMI is configured according to the Linux Setup Guide (except for git credentials, see below).

We can choose our type on the bookmarks page (micro is fine for getting started), then click "Review and Launch". If we're happy with the details we can then press "Launch". We'll be asked to manage key pairs (we can create one if we don't have one), after which we can click the "Launch Instances" button.

Logging on to the instance

After a short wait our instance will have initialized, we grab it's public IP from the console and then login to our instance via SSH

chmod 400 <keysfile.pem>
ssh -i <keysfile.pem> ubuntu@<public ip>

Upgrading Node

If Node is out of date (check node --version against <nodejs.org>), a great way to quickly upgrade is to run the following in our terminal

sudo npm i -g n
sudo n latest

Github

nscale uses both and git and Github extensively, in order for commands like nsd system clone to work. We need to have the git user name and email set to our Github login and have ssh-keys set up with Github.

To set our Github use and email we do:

git config --global user.name "<user name>"
git config --global user.email "<email>"

To generate keys:

ssh-keygen -t rsa -C "<email>"

Finally we can copy the contents of id_rsa.pub (having chosen where to store it with ssh-keygen) to Github (see Adding SSH keys to Github for help).

We can test if our keys are correctly set up like so:

ssh -T -o "VerifyHostKeyDNS yes" [email protected]

If we're correctly set up, Github will respond that we're succesfully authenticated.

Next Steps

⚠️ **GitHub.com Fallback** ⚠️