Book Image

Simplifying Hybrid Cloud Adoption with AWS

By : Frankie Costa Negro
Book Image

Simplifying Hybrid Cloud Adoption with AWS

By: Frankie Costa Negro

Overview of this book

The hybrid edge specialty is often misunderstood because it began with an on-premises-focused view encompassing everything not running inside the traditional data center. If you too have workloads that need to live on premises and need a solution to bridge the gap between both worlds, this book will show you how AWS Outposts allows workloads to leverage the benefits of the cloud running on top of AWS technology. In this book, you’ll learn what the Edge space is, the capabilities to look for when selecting a solution to operate in this realm, and how AWS Outposts delivers. The use cases for Outposts are thoroughly explained and the physical characteristics are detailed alongside the service logical constructs and facility requirements. You’ll gain a comprehensive understanding of the sales process—from order placement to rack delivery to your location. As you advance, you’ll explore how AWS Outposts works in real life with step-by-step examples using AWS CLI and AWS Console before concluding your journey with an extensive overview of security and business continuity for maximizing the value delivered by the product. By the end of this book, you’ll be able to create compelling hybrid architectures, solve complex use cases for hybrid scenarios, and get ready for your way forward with the help of expert guidance.
Table of Contents (14 chapters)
Part 1: Understanding AWS Outposts – What It Is, Its Components, and How It Works
Part 2: Security, Monitoring, and Maintenance
Part 3: Maintenance, Architecture References, and Additional Information

Monitoring Outposts

You are now confident and enabled to implement security and compliance around your hybrid architecture. Internal security threats originating within an organization from a current or former employee, a contractor, or a business associate are often underestimated.

No company is static; change is the only constant. It is not enough to create a process and train people to do the right thing; you also have to make sure people are not engaging in any wrongdoing behind your back. Moreover, it is not only people that fail; hardware also fails. Systems are designed to operate within certain limits, but what happens when the upper or lower limits are breached?

The obvious answer is that you must act in response to these events, but how can you become aware that something is happening within your walls? The answer is that you must monitor and be alerted about these events, which is what this chapter is about. It will cover the following:

  • Monitoring the capabilities...