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)
1
Part 1 Driving Transformation through AWS and DevOps
5
Part 2 Faster Software Delivery with Consistent and Reproducible Environments
9
Part 3 Security and Observability of Containerized Workloads
13
Part 4 Taking the Next Steps

Understanding your organization’s cloud operating model

Every organization is structured differently. Typically, there are three working models commonly seen across IT organizations with different levels of cloud and DevOps maturity. Some key behaviors that define which model is in use are as follows:

  • Who develops the software?
  • Who operates the software?
  • Who builds the cloud platform?
  • Who operates the cloud platform?

Focusing on sustaining workloads with the traditional approach

Traditionally, there are dedicated teams that own each of the areas described previously. The software developers build an application and then pass it over to another team for maintenance and operations. Cloud infrastructure also follows a similar pattern where certain teams build, and others run the platform. This setup is indicative of a lack of DevOps maturity and hinders growth and ownership. Software teams that function with such siloed approaches don’t have...