Chef model of managing machine state compared to Puppet

view story

http://serverfault.com – I'm deploying a web app on AWS. I intend to use chef to build AMIs which I'll then put into production. I'll update my CloudFormation template to tell AWS to use these AMIs for auto-scaling groups whenver I build a new AMI. The AMIs will have chef-solo on them which will monitor a URL to pick up changes to code/configs to deploy (at least that's the plan. Is this possible?), but I also want a way to push these changes out to instances when I decide to do a release. I'm trying to think of a good, convenient way to manage pushing out config changes so I don't have to rebuild an AMI for every (HowTos)