In case you didn't scroll to the bottom of the latest AWS newsletter, Amazon has released a new CLI (command line interface) to control your AWS NTER servers remotely. This type of tool (an older version) is how the hub.nterlearning.org started up your servers (if you followed that process).
While Amazon's CLI instructions are quite good, there are a couple of best practices I'll suggest. I'm using Mac OSX, but this will work for all of the other supported OSes.
Login to AWS and select 'Security Credentials' under the pulldown in the top right (typically your name). There you will see Access Keys. If you didn't keep these when you first created them, at the time of this writing, AWS still provides a link to download the secret key.
On your local machine, in your home directory, create .aws/config
[default]aws_access_key_id=<copy in your Access Key ID>aws_secret_access_key=<copy in your Secret Access Key>region=us-east-1output=table
Note the region needs to be updated to the region where your instances live (other options are us-west -1 and us-west-2). Also I like the output to be printed as a table, but Text and JSON (the default) are options.
A best practice would be to restrict the permissions on this file to read/write only for this user (e.g. chmod 600 for Unix based OSes).
Buried in the AWS document is a reference to a command line JSON parser called JQ. Has anyone used this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In case you didn't scroll to the bottom of the latest AWS newsletter, Amazon has released a new CLI (command line interface) to control your AWS NTER servers remotely. This type of tool (an older version) is how the hub.nterlearning.org started up your servers (if you followed that process).
While Amazon's CLI instructions are quite good, there are a couple of best practices I'll suggest. I'm using Mac OSX, but this will work for all of the other supported OSes.
Login to AWS and select 'Security Credentials' under the pulldown in the top right (typically your name). There you will see Access Keys. If you didn't keep these when you first created them, at the time of this writing, AWS still provides a link to download the secret key.
On your local machine, in your home directory, create .aws/config
Note the region needs to be updated to the region where your instances live (other options are us-west -1 and us-west-2). Also I like the output to be printed as a table, but Text and JSON (the default) are options.
A best practice would be to restrict the permissions on this file to read/write only for this user (e.g. chmod 600 for Unix based OSes).
Buried in the AWS document is a reference to a command line JSON parser called JQ. Has anyone used this?