Book Image

AWS DevOps Simplified

By : Akshay Kapoor
Book Image

AWS DevOps Simplified

By: Akshay Kapoor

Overview of this book

DevOps and AWS are the two key enablers for the success of any modern software-run business. DevOps accelerates software delivery, while AWS offers a plethora of services, allowing developers to prioritize business outcomes without worrying about undifferentiated heavy lifting. This book focuses on the synergy between them, equipping you with strong foundations, hands-on examples, and a strategy to accelerate your DevOps journey on AWS. AWS DevOps Simplified is a practical guide that starts with an introduction to AWS DevOps offerings and aids you in choosing a cloud service that fits your company's operating model. Following this, it provides hands-on tutorials on the GitOps approach to software delivery, covering immutable infrastructure and pipelines, using tools such as Packer, CDK, and CodeBuild/CodeDeploy. Additionally, it provides you with a deep understanding of AWS container services and how to implement observability and DevSecOps best practices to build and operate your multi-account, multi-Region AWS environments. By the end of this book, you’ll be equipped with solutions and ready-to-deploy code samples that address common DevOps challenges faced by enterprises hosting workloads in the cloud.
Table of Contents (19 chapters)
Part 1 Driving Transformation through AWS and DevOps
Part 2 Faster Software Delivery with Consistent and Reproducible Environments
Part 3 Security and Observability of Containerized Workloads
Part 4 Taking the Next Steps

Pets versus cattle

In the old way of doing things, servers were always cared for, lovingly nurtured, and given pet names such as Atlantis, Raptor, Battlestar, and so on. These were standalone systems that hosted critical applications, were monitored 24/7, and required administrators to nurse them as soon as issues were identified. The smallest of problems with these systems meant some part of the organization would not function, or external customers would be impacted. The nature of how these systems were perceived and maintained was similar to how we treat pets – with utmost care and affection. You cannot just replace them; instead, you must fix the underlying problem and get them healthy again. The application developers also operated with a similar mindset in terms of rolling out changes to these servers. They would keep track of all changes, execute scripts in a particular order, and define runbooks for all expected scenarios. Such an approach to maintaining critical systems...