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

Outposts Maintenance

Monitoring your Outposts is a critical administrative task. Outposts resources are finite, especially if you are used to the virtually unlimited capacity of an AWS Region. Customers can make the mistake of not planning the AWS Outposts capacity and run into an Insufficient Capacity error whenever it runs out of capacity to provision resources. Additionally, service link interruptions, as well as S3 and EBS (Elastic Block Store) consumption, must be monitored.

If you have an established monitoring practice, you may be able to proactively react before something bad happens most of the time. Generally, you will be able to fix the cause of alarm yourself, for example, shutting down non-productive instances, deleting stale volumes, or deleting unnecessary S3 objects in a bucket.

However, as AWS CTO Werner Vogels said, “Everything fails, all the time.” It’s an inconvenient truth that any physical hardware will inevitably degrade to a point...