The Hub will pull out the activation key automatically from the URL and verify everything is setup on Amazon's side.

If the message about Amazon validating your payment details still appears, then there might be an extra long lag on Amazon's side, or there really is something wrong with the payment details.

In this case, unfortunately, there isn't anything we can do from our side. I can only recommend "hanging tight" and doing the dp-activate thing again a little later... Alternatively, you might want to contact Amazon to get them to take a look at your account.

Mine was working and now it is not. I followed your suggestions, but TKLBAM / EC2 is not listed in dp-activate. I think you need to turn my TKLBAM off in the hub, so that I can start from scratch with TKLBAM.

I have a question: We currently have a Micro EBS-backed server, let's say my EBS volume is called "vol1". Is the data stored on the EBS volume indep from the instance no? I mean can I consider my ebs volume a "backup", meaning I can destroy my instance safely and create a new instance and link it to the former's EBS volume (vol1). Correct?

Guys I got a reply from amazon: they ask me to cancel and re-submit my application to the TKL instance.

I can do it but I thin I will lose the instance and I don't have any backup. OR I can safely cancel and resubmit without losing access to the instance? Please let me know!

P

---

Can you please cancel out and re-subscribe to the application with a valid credit card. Here's how:

1. Go to http://www.amazon.com/dp-applications and log in.
2. Confirm that your subscription is in "Activation Pending" mode. Click on the "View/Cancel application" link under the name of the product.
3. On the page that comes up, click on "Cancel the use of application."
4. After you have canceled out of the product, go back to the page where you subscribed to the application and re-subscribe with a valid credit card.

To do this, ultimately it will depend on what your appliance is, but basically the best way to go IMO would be to dump the database (if that's relevant) and then rsync the DB dump and any relevant data files to a local instance.

If you can give more details I can offer some more specific suggestions, but personally I'd rsync to a local instance (running as a VM) so you can make sure that it all works as it should before you risk losing it.

Or another possiblility (I'm not 100% about this) but I'm fairly sure you should be able to create a whole new account, then once it is set up and working as it should then add your new account's TKLBAM API to your old server and run a backup, then restore to a fresh instance (on your new account). Once you have confirmed all works as it should, then destroy your old server and cancel your old account.