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

Network troubleshooting

The network substrate is a critical component of any IT architecture. Whenever your design requires a certain condition, the optimal performance depends on that condition being fulfilled. AWS Outposts has stringent networking requirements, and only only smooth network operations will allow the service to operate with peak performance.

The service link is a critical function and must be thoroughly monitored. If you receive an alert that your link is down, there are various actions that you can carry out to expedite the troubleshooting process because the problem’s root cause might be on your end. To explore potential sources or problems, let’s use as reference Figure 7.1, which depicts Outposts networking logical components:

Figure 7.1 – AWS Outposts network logical diagram

Here is a checklist of potential causes of a LINK DOWN alarm on your end.

Instability or failure of your customer’s device