29 Posts tagged with aws
Panda - Open source video platform
Running MySQL on Amazon EC2 with Elastic Block Store
Amazon Web Services Premium Support
Persistent Storage for Amazon EC2
scalr
Announcing Thrudb EC2 Public AMIs
DeHorrible: RESTifying SimpleDB
Amazon SimpleDB
Cache-Control Header for Amazon S3
Thumbnail
Amazon Web Services Blog: Amazon EC2 Gets More Muscle
Jake@Nitobi » Blog Archive » RobotReplay and Rails on Amazon EC2
Live Blogging with Amazon S3
Capazon 0.2 Released - Capistrano 2.0 Compatible
Capazon 0.2.0 is out. There’s only one new feature: support for Capistrano 2.0. There’s no backwards compatibility. If you’re still on Capistrano 1.4.x, please don’t upgrade. It won’t work.
To update Capazon:
gem install capazon
Changes
Capistrano 2.0 has support for Rake-like namespaces, so I’ve moved all tasks provided by Capazon to the ec2 namespace:
$ cap ec2:describe_images
* executing `ec2:describe_images'
IMAGE ami-0386636a rbuilder-online/nuxleus-1.3-x86_9327.img.manifest.xml 099034111737 available true
IMAGE ami-0683666f rbuilder-online/fedoracore6-1.0-x86_9677.img.manifest.xml 099034111737 available true
[...]To call these tasks from another namespace in a Capistrano recipe:
namespace :whatever do
task :something_cool do
[...]
ec2.describe_images
[...]
end
endCapistrano 2.0
Turns out updating extensions to work w/ Capistrano 2.0 is extremely easy. Just replace blocks like this:
Capistrano.configuration(:must_exist).load do
task :take_over_the _world do
[...]
end
end...with this:
Capistrano::Configuration.instance.load do do
task :take_over_the _world do
[...]
end
endFor more on upgrading your recipes to Capistrano 2, head over to the upgrade guide on Capistrano’s new website or this post on NubyOnRails. Happy capifying!
Amazon Web Services: Start-Up Seattle Notes
Last Thursday’s Start-Up Seattle event put on by the Amazon Web Services Team and Medrona Venture Group was an enlightening look at the endless possibilities Amazons Web Services present to small companies. Even though I’m fairly familiar with the inner workings of Amazons Web Services – this blog is hosted on an EC2 instance, and I recently released Capazon, a Capistrano extension library to manage EC2 instances – this event shed new light on how much they mean to the internet.
Jeff Barr, Amazons Web Services Evangelist, revealed that in Amazon’s research, engineers at small web-based companies revealed that they spent only 30% of their time developing features unique to their product. The other 70% was spent doing “undifferentiated heavy lifting”: buying and configuring hardware, dealing with data centers, implementing load balancing solutions, and dealing with growth issues. With these issues being handled by Amazons Web Services, small companies are able to focus more of their time on their product’s unique features instead of repeating the work of others throughout the world.
This, in effect, shifts downward the cost of starting a new company, or cycling the improvement loop in an existing company. There’s no hardware to buy, no hard drives to swap, no data centers to visit – only time spent on the core product itself.
Andy Jassey, Amazons Web Services Senior Vice President, revealed something very interesting: Amazon is no longer offering these services with excess capacity at Amazon’s data centers, rather, they are actively purchasing new hardware dedicated to Amazons Web Services. “We’re going to scale Amazons Web Services as big as users demand”, he said in response to a question pertaining to the capacity Amazon has to offer.
I also had a great chat with Matt Garman, Amazon Web Services Product Manager, during the wine tasting after the event.
I emerged from this event with pages and pages of notes detailing how LexBlog could use Amazon Web Services for future product offerings, and even to replace a good bit of our current hardware. Events like these are few and far between, and I consider myself very lucky to have been able to attend.