Book Image

Implementing Cloud Design Patterns for AWS - Second Edition

By : Sean Keery, Clive Harber, Marcus Young
Book Image

Implementing Cloud Design Patterns for AWS - Second Edition

By: Sean Keery, Clive Harber, Marcus Young

Overview of this book

Whether you're just getting your feet wet in cloud infrastructure or already creating complex systems, this book will guide you through using the patterns to fit your system needs. Starting with patterns that cover basic processes such as source control and infrastructure-as-code, the book goes on to introduce cloud security practices. You'll then cover patterns of availability and scalability and get acquainted with the ephemeral nature of cloud environments. You'll also explore advanced DevOps patterns in operations and maintenance, before focusing on virtualization patterns such as containerization and serverless computing. In the final leg of your journey, this book will delve into data persistence and visualization patterns. You'll get to grips with architectures for processing static and dynamic data, as well as practices for managing streaming data. By the end of this book, you will be able to design applications that are tolerant of underlying hardware failures, resilient against an unexpected influx of data, and easy to manage and replicate.
Table of Contents (20 chapters)
Title Page
Dedication
About Packt
Contributors
Preface
Free Chapter
1
Introduction to Amazon Web Services
Index

Vulnerability scanning


Traditional scanning is not really required in the cloud if you follow best practices. Establishing a defense-in-depth posture will frustrate most of the script kiddies. Rotation of sensitive material diminishes the likelihood of an Advanced Persistent Threat (APT) getting a foothold. However, your product is software and odds are that it uses some open source code (who has time to rewrite everything?). Moving security into the early stages of the SDLC allows us to catch problems before they can be exploited in a production system. We also need to ensure the contents of the Terraform state file are consistent.

Instance-level scanning

We are not huge fans of instance-level scanning, but if you have to do it, AWS Inspector works well. I think that automating updates of your instances when new, patched versions appear is a better way to go. In part two, we'll build out a pipeline to demonstrate this process.

 

Containers

Workload containerization is also changing the security...