Tactical edge – Architecting for Disconnected Edge Computing Scenarios

Tactical edge refers to edge computing environments that support military operations. Such situations are characterized by limited connectivity, high mobility, and the most intense security requirements. At the tactical edge, the most common needs include deploying, managing, and securing the following technologies: IoT: Cameras and sensors of every description get cheaper every day. The number […]

Moving Greengrass to the SATCOM terminal – Architecting for Disconnected Edge Computing Scenarios

Imagine a situation like we had in the previous section where we want to put an IoT gateway in the middle of nowhere behind a SATCOM terminal, but for various reasons, AWS Snowcone isn’t ideal. Maybe we intend to deploy it once and never physically visit the site for 5 years. How could we run […]

Understanding AWS IoT Greengrass relationships – Architecting for Disconnected Edge Computing Scenarios

The following figure provides an overview of the relationship between the multiple logical constructs you must configure within the AWS IoT Core and AWS IoT Greengrass services in-region. Remember, all the Greengrass v2 agent does is dial home and fetch its configuration from AWS. This includes the components (software) it needs to download from S3 […]

Overview of DDIL – Architecting for Disconnected Edge Computing Scenarios

In this chapter, we will explore some of the most challenging edge computing scenarios – that is, those where connectivity back to an AWS region might be intermittent or non-existent. It is difficult to effectively run a globally distributed system when the endpoints aren’t consistently reporting back. Even in such circumstances, AWS services allow customers […]

Amazon CloudFront Embedded POPs – Utilizing the Capabilities of the AWS Global Network at the Near Edge

In addition to the 450+ edge POPs that AWS maintains around the world, there are additional dedicated POPs positioned inside the networks of many ISPs/broadband providers around the world. These are known as Amazon CloudFront Embedded POPs, and they are based on AWS Outposts Rack or AWS Outposts Server (depending on the circumstances). Figure 8.8 […]

Content distribution – Utilizing the Capabilities of the AWS Global Network at the Near Edge

Amazon CloudFront uses a construct known as distributions to establish and govern this behavior. When a new distribution is created, it is pointed at an origin – this is the server or service that holds the content we want to cache in our POPs. Amazon CloudFront supports several types of origins – including S3 buckets, […]

Availability Zones (AZs) – Utilizing the Capabilities of the AWS Global Network at the Near Edge

To understand the full benefits of utilizing the AWS global backbone, we must first start at the foundational units that make up the AWS cloud – AZs. CLOS (leaf/spine) topology The physical network fabric in AZs is a fully Layer 3 CLOS architecture, also known as a leaf/spine design. To simulate Layer-2 adjacency between EC2 […]

Overview of the AWS Global Network – Utilizing the Capabilities of the AWS Global Network at the Near Edge

The AWS Global Network is the cornerstone of everything AWS does. It represents an expansive and cutting-edge infrastructure designed to offer unparalleled performance, reliability, and security. It’s more than just a network; it’s a testament to AWS’s commitment to delivering a seamless cloud experience to businesses and end users across the world. By understanding and […]

Traffic dials for endpoint groups/regions – Utilizing the Capabilities of the AWS Global Network at the Near Edge

By default, these are set to 100% for all endpoint groups attached to a listener. This results in the default behavior where connections always go to the closest region. When these values are altered, things can get a little tricky to understand, so let’s walk through some examples: Figure 8.20 – AWS Global Accelerator traffic […]

Amazon CloudFront functions – Utilizing the Capabilities of the AWS Global Network at the Near Edge

As noted previously, AWS Lambda@Edge functions execute inside the RECs. That’s better than having to run them in the core regions – but what can we do inside the edge POPs themselves? That is where we must use Amazon CloudFront functions: Figure 8.13 – Visualization of where Amazon CloudFront functions and AWS Lambda@Edge run These […]

TOP