in case of the "create_snapshot" and "update_snapshot" deletion policies, once an instance is stopped, an EBS volume was deleted even if there was an error or timeout (10 minutes) during a snapshot creation
the "onDemandInstance" parameter wasn't working if the old configuration used
the "spotty start" and "spotty status" commands were failing if an on-demand instance was used (but the instance itself was working)
if the "subnetId" parameter was specified, an AMI creation didn't work
displaying a proper error message if the user is trying to connect to an instance without a public IP address
Bug fixes: