This is a slightly advanced topic, but if you ever wanted to tweak Scott's AMI (to add software or change configuration of the OS slightly, or whatever), what happens is that you have to save the AMI and then store it in S3, before shutting down the instance. (Otherwise you will lose all of your changes) I found it tedious to repeatedly type in the command-line commands for the EC2 API to accomplish this, so I wrote 3 little bash scripts that are wrappers to the EC2 commands that helped me to remember what information to pass to the commands.
Execution Sequence
1) Run upload_certs.sh - this copies your public & private AWS keys to the instance that you've already started.
2) Run wrap_up.sh - this executes a series of commands that bundle up the targeted instance and store it in your S3 storage, so that you can use the image later when you want to bring up that instance.
3) delete_bundle.sh - this deletes old versions of your image that you don't want to pay to keep stored in S3.
Of course, all of these scripts require you to edit some of the fields to make them conform to your unique AWS account info. (for example -b field should be populated by the bucket name you choose for your company, instead of "crosspath") Also, these scripts require that you have the AWS command line tools on the machine where you run these scripts.