Exactly. Since the main issue seems to be the customizing of the web environment, I would recommend making a chef recipe and keep it on their cloud service. Then, when you need a new instance, load on the chef client and config and have it do all of the work. Later on, you can start worrying about custom images or hosting your own chef server.
I'll need to echo this. They also have Broadcom NICs with TOE + iSCSI offload. I use some Dell blades with a dual head Sun 7410 system and that runs Citrix XenServer running Debian squeeze VMs plus some windows VMs. The blades are built to have redundant NICs and room for up to two more network types. Whether it's ethernet, fiber channel, ininiband, etc. Plus the network modules in the blade chassis can be switches themselves. Plus the range of product options is pretty good too.
While photos are fairly easy to duplicate, registering them with the copyright office shortly after taking them is a pretty powerful argument when people use them outside of the attributions you license them with. If a site is infringing on their work, tell them to ask their lawyer about going to court over a registered copyright and they'll settle real quick. It's the difference between $500 and $50,000 if it ever goes to court. This does several things. 1) it demonstrates that you took the photo. 2) That you are asserting copyright (and quickly at that) 3) opens up the infringers to further damage apart from time and materials. There's a recent book on photography and copyright that's a good reference.
Back in the 90's, I had an accounting professor who did her whole class in PowerPoint. When I signed up and got the text books and I also needed to buy a packet of paper which had the whole semesters worth of PP slides with plenty of room to take notes. This way I never had to write down what was on the slides themselves, just my understanding of the material. And there was a lot of material.