Ansible is dead, Long live AWS Beanstalk

Photo by William Krause on Unsplash

All configuration management systems suck in equal measure, but each in a different fashion. Pick the one that sucks the least for your particular use-case and hope that two years down the line you made the right choice.

Ansible is hard

Configuration management also seems to be the place most people want a “standard” for. “Just tell us how to do it,” the phrase uttered from many teams who are using Ansible realize the level of work they will need to do to figure out where to start.

Ansible is hard because;

  • Everyone in your team must commit to the process.
  • It depends on the organizational context.
  • It may require significant organizational change AND individual change (e.g., Learning Ansible)

All configuration management systems suck in equal measure, but each in a different fashion. Pick the one that sucks the least for your particular use-case and hope that two years down the line you made the right choice.

Developer productivity

Agile and easy to begin

You simply use the AWS Management Console, a Git repository, or an integrated development environment (IDE) such as Eclipse or Visual Studio to upload your application, and Elastic Beanstalk automatically handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring. Within minutes, your application will be ready to use without any infrastructure or resource configuration work on your part.

Conclusion

∞ Travel | Coding | Lifestyle ⦿ Bangkok | ✧ #freelancer ▷ Got a project? ⭣ www.upwork.com/fl/al3rez