Content delivery networks are all the rage now, so I’m looking at creating a CDN that will work nicely with my WordPress installation.
Rather than just blindly use a plugin, I want to make the code trustworthy and reusable among other blogs that I manage. Certainly the easiest way to get a CDN working on your blog is to use the Jetpack plugin from Automattic. This transparently turns the content on your blog into a CDN-delivered bowl of web content.
Some people might not want the full weight of the Jetpack plugin or to use the WordPress CDN so here we go. I’m going to step through the process that I used to get a CDN working myself. Continue reading Getting Started With Amazon As a CDN – Part 1
I’m often switching between different Amazon AWS accounts. So to speed things along I’ve set up some simple scripts to easily switch between accounts while at the command line
On Linux (aws_setup):
Once saved, run
chmod +x aws_setup
On Windows (aws_setup.cmd):
Save as many files with the paths to your various AWS key pairs, and simply run the script from within a terminal before using the ec2 tools.
NOTE, when you run the scripts on Linux (and I guess Macs), add an extra dot before you run it. This will allow the environment variable to persist when the script ends.
Here are some simple commands to get you started with using Amazon EC2:
Displays your account’s AMIs that are on Amazon
This launches your Amazon EC2 instance. Use your own or one of Amazon’s AMI IDs
Describes your running instances with AMI and instance IDs
Lists your account’s volumes and their status
ec2attvol vol-XXXXXXXX -i i-XXXXXXXX -d xvdf
Attaches an Elastic Block Storage device to your running instance
Detaches the storage volume from an instance (use -f to force)
Stops a running instance so that you can perform maintenance on it
Modifies an instance attribute such as the instance type
Resumes your stopped instance
Terminates your running instance