So, we use lots of cloudformation. Amazon's cfn-init scripts kinda suck, since they don't act like blueprint does in all cases -- especially when you want to use a blueprint to update a box. So, we built this little tool to allow someone to easily pull the metadata section of the LaunchConfiguration and execute it with normal blueprint. Right now, we kick these updates semi-manually, with fabric. In the near future, we'd very much like to have a daemon that subscribes to the SNS channel monitoring changes to the stack (or poll, if desired.)
Boto is required to run blueprint-cfn, but we didn't add it as a requirement to the blueprint project -- we just print out a message instructing the user to install it.
So, we use lots of cloudformation. Amazon's cfn-init scripts kinda suck, since they don't act like blueprint does in all cases -- especially when you want to use a blueprint to update a box. So, we built this little tool to allow someone to easily pull the metadata section of the LaunchConfiguration and execute it with normal blueprint. Right now, we kick these updates semi-manually, with fabric. In the near future, we'd very much like to have a daemon that subscribes to the SNS channel monitoring changes to the stack (or poll, if desired.)
Boto is required to run blueprint-cfn, but we didn't add it as a requirement to the blueprint project -- we just print out a message instructing the user to install it.