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 instances

It has been an amazing journey so far. We have a thorough understanding of Outposts, the anatomy of the rack, and how to select, order, and have one delivered to us. It is time to head on to the AWS Console and play with our Outposts, which should now show the status as Active in the service page summary:

Figure 4.1 – AWS Outposts Summary page

Before we move further, there is a very important distinction to make: Availability Zone versus Availability Zone ID. As we know, AWS creates an abstraction to prevent Availability Zones from being saturated by mapping real Availability Zone IDs (usw2-az1, shown in Figure 4.1) to different Availability Zones in the console (us-west-2a, shown in Figure 4.1) for distinct AWS accounts.

As an example, you can have two AWS accounts, A and B. AWS account A can have the mapping mentioned earlier, and AWS account B can have the us-west-2a Availability Zone mapped to Availability Zone ID usw2-az3...