Book Image

Accelerating DevSecOps on AWS

By : Nikit Swaraj
Book Image

Accelerating DevSecOps on AWS

By: Nikit Swaraj

Overview of this book

Continuous integration and continuous delivery (CI/CD) has never been simple, but these days the landscape is more bewildering than ever; its terrain riddled with blind alleys and pitfalls that seem almost designed to trap the less-experienced developer. If you’re determined enough to keep your balance on the cutting edge, this book will help you navigate the landscape with ease. This book will guide you through the most modern ways of building CI/CD pipelines with AWS, taking you step-by-step from the basics right through to the most advanced topics in this domain. The book starts by covering the basics of CI/CD with AWS. Once you’re well-versed with tools such as AWS Codestar, Proton, CodeGuru, App Mesh, SecurityHub, and CloudFormation, you’ll focus on chaos engineering, the latest trend in testing the fault tolerance of your system. Next, you’ll explore the advanced concepts of AIOps and DevSecOps, two highly sought-after skill sets for securing and optimizing your CI/CD systems. All along, you’ll cover the full range of AWS CI/CD features, gaining real-world expertise. By the end of this AWS book, you’ll have the confidence you need to create resilient, secure, and performant CI/CD pipelines using the best techniques and technologies that AWS has to offer.
Table of Contents (15 chapters)
1
Section 1:Basic CI/CD and Policy as Code
5
Section 2:Chaos Engineering and EKS Clusters
9
Section 3:DevSecOps and AIOps

Planning your fully private EKS cluster

In this section of the chapter, we will outline the points that are required to create a secure, scalable, and highly available production-grade EKS cluster. We created an EKS cluster using eksctl in the previous chapter, which was a two-node Kubernetes cluster. We can't use that cluster to deploy a production workload. Let's understand the requirements for an EKS cluster that can support a production workload. The following considerations need to be made, which will be covered in planning:

  • Networking: Network planning will be the backbone of your EKS cluster. You need to understand all the pain points related to VPC CNI and VPC endpoints. We use VPC CNI because it has wonderful IP address management with the IP address available within the VPC. This means even the Pods get the IP address of the subnet. VPC endpoints will be used for the private cluster, where the worker nodes sitting in the private subnet need to talk to the...