mr.awsome is a commandline-tool (aws) to provision, manage and control server instances.
What kind of server instances these are depends on the used plugins.
There are plugins for EC2 (mr.awsome.ec2), FreeBSD Jails (mr.awsome.ezjail) and more.
You can create, delete, monitor and ssh into instances while mr.awsome handles the details like ssh fingerprint checking.
Additional plugins provide advanced functionality like integrating Fabric (mr.awsome.fabric) and Ansible (mr.awsome.ansible).

The default user for ssh connections. If it’s set to * then the current
local user name is used.

port

The ssh port number.

fingerprint

(required) The ssh fingerprint of the server.
If set to ask then manual interactive verification is enabled.
If set to ignore then no verification is performed at all!

password-fallback

If this boolean is true, then using a password as fallback is enabled if the
ssh key doesn’t work. This is off by default.

password

Never use this directly! If password-fallback is enabled this password is
used. This is mainly meant for Fabric scripts which have other ways to get
the password. On use case is bootstrapping FreeBSD
from an mfsBSD distribution where the password is
fixed.

proxyhost

The id of another instance declared in aws.conf which is used to create a
tunnel to the ssh port of this instance.

proxycommand

The command to use in the ProxyCommand option for ssh when using the assh
command. There are some variables which can be used:

path

The directory of the aws.conf file. Useful if you want to use the assh
command itself for the proxy.

known_hosts

The absolute path to the known_hosts file managed by mr.awsome.

instances

The variables of other instances. For example: instances.foo.ip

In addition to these the variables of the instance itself are available.

mr.awsome provides an additional tool assh to easily perform SSH based
operations against named instances. Particularly, it encapsulates the
entire SSH fingerprint mechanism. For example EC2 instances are often
short-lived and normally trigger warnings, especially, if you are using
elastic IPs.

Note:: it does so not by simply turning off these checks, but by transparently updating its own fingerprint list using mechanisms provided by the backend plugins.

The easiest scenario is simply to create an SSH session with an instance. You
can either use the ssh subcommand of the aws tool like so:

aws ssh SERVERNAME

Alternatively you can use the assh command directly, like so:

assh SERVERNAME

The latter has been provided to support scp and rsync. Here are some
examples, you get the idea: