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

The physical security of Outposts

After understanding how AWS Outposts integrates seamlessly with the AWS ecosystem of security services and uses its capabilities, let’s talk about the physical security of Outposts hardware.

This may be a new topic for some of you, especially for cloud-native professionals. You don’t get into these details when you build in the Region. You know that, of course, there is hardware somewhere in AWS data centers but it is AWS’s responsibility to keep it secure and running.

When operating within the AWS Region, customers are bound by the AWS Shared Responsibility Model. The purpose of this statement is to clearly demarcate who is responsible for what when you select the AWS platform to run your applications. By operating under this framework, the customer is relieved from any operational burden in regard to facilities supporting the cloud operations.

AWS defines this model by stating “AWS is responsible for security...