Sugar 0.4.0: Server SSH key verification, autodetected username

Sugar now consults the server console to detect the SSH hostkey fingerprints, stores them in an EC2 tag for future reference, and adds the keys to the local system to bypass the yes/no prompt while improving security. It also auto-detects the username to use when connecting to the server.

This feature is still somewhat experimental. Please report any issues you come across.

Update with npm install -g sugar-ssh

Sugar 0.3.3: More flags, more usefulness

This release adds a bunch of flags that extend the usability of Sugar to embedding in shell scripts and the like. Most notably user overrides and --dns for just getting an instance hostname.

0.3.2: Selection by public or private DNS/IPs

Fixes issue #2

0.3.1: Version reporting and public IP fallback

This release fixes issues #4 (failure on instances without public DNS) and #5 (--version flag). It also adds a first-class --help flag.

0.3.0: Simple port forwarding via `-f`

Sugar 0.3.0 adds support for basic port forwarding, allowing you to bring a server's port to your localhost.

Example: sugar -f 3000 httpd will bring your http server's 3000 port to localhost:3000. Useful if your instances are behind load balancers. Sugar will also select a random httpd server if you have multiple with the same name.

0.2.3: Add SSH_USER and SSH_KEY envvars

Sugar 0.2.3 supports arbitrary SSH user and private key selection via environment variables:

• SSH_USER: username on the server (normally ubuntu or ec2_user, ubuntu is default)
• SSH_KEY: path or name of a private key file to use

0.2.0: Support .pem extensions

When looking for private keys, sugar now tries both of:

• ~/.ssh/<keypairname>
• ~/.ssh/<keypairname>.pem

This matches how AWS gives PEM files to the user.

Sugar 0.1.4

v0.1.4

Bump version to 0.1.4