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

Working with shared resources

Let’s close this chapter with a look at how we share resources across different accounts. AWS Outposts is compatible with AWS Resource Access Manager (RAM), a service that securely allows AWS accounts, AWS Organizations, or organizational units (OUs) within an organization to consume resources shared by another account. Better yet, AWS RAM is available to you at no cost.

The account sharing the resources is denoted as the owner, while the accounts using these resources are the consumers. With this model, you can design one AWS Organization and order your Outposts in the root account and share its resources with OUs or member accounts directly. Here is an example of a basic organization:

Figure 4.13 – Basic AWS Organization design

There are services that can run on Outposts but cannot be shared. A comprehensive list of resources that can be shared is available at this URL: