At the moment of the experiment we did not have a Credit Card near the expiration point (that will be presented in a later post) laying around. Thus we use another technique to provide a close reality check between Amazon as a Cloud Provider and the relation of your data and their money. We proceeded in the following way:
- Created an Amazon account with a Credit Card.
- We subscribed in EC2 and S3 services from amazon.
- We turned on EC2 windows and Linux instances.
- We created EBS drives and hook them with the Linux and EC2 instances.
- We setup basic web servers and MySQL databases for each instance.
- We created backups from the MySQL into S3 and also filesystem level backups in S3.
- We waited about a month. Before the Amazon bill was ready, we call our CC provider and ask them to block all charges from Amazon.
- Waited until Amazon charge us and block our account.
After Amazon tried charging our credit card and the American Express bank refuse the bill, our Amazon AWS login did not work anymore. For our surprise, our AWS keys kept working. So we were able to:
- Download and upload data into S3.
- Keep managing instances of EC2.
- Using all our instances services (Database, WebServer, and others).
Tips for Keeping your AWS Services Running:
- Always use a second credit card in the account registration as a backup.
- As a contingency plan keep your data located in a different place than your cloud provider.
- Do not trust the data storage, always use some type of encryption.