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

Structural elements – rack and power

Now that we have a deep understanding of the edge space and how AWS Outposts addresses use cases in this realm, it is finally time to take a look at Outposts itself and break down each part. Before we jump into that, it is important to underline the statement we made in the previous chapter: AWS Outposts is not commodity hardware; it is a downscaled extension of the AWS cloud infrastructure for your data center.

This is important because a different mindset is required to get the most from this chapter. Architects designing solutions using commodity hardware often analyze certain aspects of servers, storage, and networking that are irrelevant when designing a system with AWS Outposts. I definitely want to discourage your thought process from leaning toward the following:

  • Processor models and features, number of cores, L2 and L3 caches, stepping, and families
  • Networking chipsets and features
  • Drive types, sizes, interfaces...