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 local gateways

Our EC2 instance is now running on AWS Outposts and is capable of communicating with the other subnets in VPC and also with the internet because it has a public IPv4 associated with it. So, what role does the local gateway play?

The local gateway (LGW) is the networking construct that allows your Outpost to communicate with the customer network, and it only exists in the rack. Outposts servers use the Local Network Interface (LNI) to communicate with the local network.

Only one LGW is created per Outpost and it can be attached to multiple VPCs within the Outpost; it operates in a Network Address Translation (NAT) fashion. This feature can add additional latency to the network traffic in extreme conditions. It’s a best practice to interact with AWS teams to assess the limitations of this structure under stress conditions and make sure it will meet your architecture requirements.

During the installation process, another type of route table...