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 with CloudWatch

After thoroughly understanding the security aspects of AWS Outposts, we will now discover how we can monitor our Outpost’s capacity and improve the user experience. We collect metrics to identify and resolve issues before they impact our customers. Remember that the capacity of Outposts is finite, and it is your responsibility to manage the resources available to you.

You don’t have access to AWS Outposts telemetry; this is the responsibility of AWS. Hardware degradation or failure should be detected by AWS teams, and the replacement process will be triggered.

You must embrace failure and design architecture to be resilient and withstand failures at various levels, potentially up to the unavailability of an entire AWS Region. However, failover procedures or election processes among nodes of a distributed application must be triggered by some sort of change in your system.

The AWS go-to service to collect metrics, monitor your systems...