Amazon Web Services and Platform as a Service: Putting it all Together

Now that all the work’s done - it’s time to play. :)

One interesting thing to try is the S3 Async demo on the iOS mobile client: this gives an example of how to upload data asynchronously to an S3 bucket.

S3 Async demo


I also wanted to try out the SNS APIs, so I used the Android client to add an SNS topic and then an email subscription: all very straightforward, here are the screen shots from the Android emulator and the email notifications I received from AWS:



SNS email subscription


SNS email

Here are listings of the S3 buckets, SQS queues and SDB domains that I created for this blog, shown using the Android mobile client - compare that with a similar view given by the webapp we created earlier:


S3 SQS SDB lists


AWS webapp
Note that the image on the left was taken when using the Anonymous TVM, which uses a SimpleDB domain to keep a record of devices accessing AWS services using the mobile client, while the image on the right was taken when using the Identity TVM, which adds an SDB domain to hold user login information.

You can go in using the AWS Management Console to inspect the various objects that you just created: the only exception is SimpleDB (SDB), which isn’t part of the AWS Management Console (yet).  If you want to look at SDB domains, here’s a useful Firefox add-on that lets you view your SDB Domains: sdbtool - don’t forget to click on the Config button to configure your AWS access credentials.

In this view, you can see the two domains (TokenVendingMachine_<app_name>_DEVICES/USERS) that are used to store the device UDID and user/password information:</app_name>

SDB tool domains

I hope you found this look at the Token Vending Machine architecture interesting - and that it has got you thinking about how powerful the combination of Amazon Web Services and Platform as a Service can be!

Mark Prichard, Senior Director of Product Management