I think more flexible is a better word -- it can do more than what you can do when you bake a static image because you also use it to dynamically manage a running system post-boot.
Ansible can deploy all of your dependencies, keep them updated, push out configuration changes, and deploy your main application code.
I don't use AutoScaling, but no reason it couldn't be used with Ansible. The docs have a bit of detail on how to do it. http://docs.ansible.com/guide_aws.html
I wrote the EC2 inventory plugin, so yes, I am a big fan of Ansible. I however, now use Ansible almost exclusively to build AMIs. Do your application code deploys require downtime, or do you have a technique to keep the service online while making changes?
I highly recommend you start using ASGs. It is only a matter of time before things go bad if you don't.
Comments
Easier in what sense? Baking, deploying, or managing the AMIs?
Also, are you using AutoScaling Groups with this methodology?
I think more flexible is a better word -- it can do more than what you can do when you bake a static image because you also use it to dynamically manage a running system post-boot.
Ansible can deploy all of your dependencies, keep them updated, push out configuration changes, and deploy your main application code.
I don't use AutoScaling, but no reason it couldn't be used with Ansible. The docs have a bit of detail on how to do it. http://docs.ansible.com/guide_aws.html
I wrote the EC2 inventory plugin, so yes, I am a big fan of Ansible. I however, now use Ansible almost exclusively to build AMIs. Do your application code deploys require downtime, or do you have a technique to keep the service online while making changes?
I highly recommend you start using ASGs. It is only a matter of time before things go bad if you don't.