Snapshot launch: manual action required

Wondering why don't I have the 'clone' option? I only have an option to create an AMI. I don't get the 'clone' option when I launch an AMI either? Thanks.

Not sure what is up with secret keys/access keys... I'm assuming that you're referring to AWS API keys? Perhaps AWS have made some changes... TBH I'm not sure if it would affect your currently running instances but I wouldn't think so... The only thing that I would be concerned about is if you are referring to SSH keys, AFAIK you can only have one SSH keypair associated with your AWS account, so if you are changing them, you may wish to also change it with your other appliances (although strictly speaking I wouldn't image it would be required...)

TBH I haven't been involved with the development of the Hub and haven't used the 'clone' functionality (I use the Hub regularly but haven't ever used snapshots - perhaps it's time I did!). Knowing what I know about ALon and Liraz (the core TKL devs) though I imagine that it would 'Just work'(TM) :)

AFAIK new servers should automatically get their own unique TKLBAM backupID. Also AFAIK all your Hub instances should be billed together. So for all intents and purposes it should be a totally independent instance. However I'll do some testing so i can be confident in my comments.

[update] I just took a snapshot of a server, and then cloned a new server from it. It gets it's own IP and it's own unique backup set (when I just ran TKLBAM manually). It inherits it's root password from the snapshot. The only things that may not be intuitive (and might trip you up if you weren't careful) is that the cloned instance also inherits it's label from the original instance [from the default label for that appliance and size] (so will look the same as the original in the Hub [assuming that you haven't changed it from the default label]) - so you'll want to manually change that. Also I had a domain name attached to my original instance and the cloned one stole that domain association on launch. So that might be something to be careful of! I'm not sure whether it would act the same if you had an elasticIP attached to your instance...? (I was just using HubDNS)

[more update] I just rebooted the original instance to see what would happen and it stole it's domain name back! So that is definitely something you'll want to manually adjust! Also I have just realised that the Label is not unique, even when you launch a new server the same (i.e. not a clone) it gets the same default label. Perhaps the clone server wasn't inheriting the original server's Label, but the default label of the appliance? I will test some more!  The cloned server inherits the default label for that instance (i.e size - appliance e.g. Small Wordpress). I have edited the original post to reflect this (crossed out the incorrect bit and added the correct info in square brackets).

We have had a few people (more than usual) having issues with signups lately so it had crossed our minds that perhaps AWS had changed something. Your post confirms it so thanks very much. We will endeavor to update the Hub docs to align with the new process.

TBH I'm not sure whether this will affect existing deployments. I hope (and expect) not...! But we will have to check it out when we do our update/upgrade.

Using the Hub's "Restore this backup to a new cloud server" feature, the effect will be somewhat like launching a new clone, however instead of using the 'snapshot' data, it uses a TKLBAM backup.

So basically it starts a new server that matches the TKLBAM profile, it goes through it's normal boot and update process, then it restores the relevant TKLBAM backup.