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 […]
Category: The Yocto Project
AWS Cloud WAN – Utilizing the Capabilities of the AWS Global Network at the Near Edge
For relatively simple, static situations like what we’ve described so far, AWS Direct Connect SiteLink is sufficient. But let’s say we want to build a SaaS offering on top of AWS that connects to physical elements at the edge. Some of these are in true data centers, with AWS Direct Connect links set up to […]
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 […]
TCP termination – Utilizing the Capabilities of the AWS Global Network at the Near Edge
It is important to remember that while AWS Global Accelerator uses IP Anycast to steer clients into the nearest edge POP, it is much more than that. In a similar way to Amazon CloudFront, when customer connections enter an edge POP, they are terminated on a proxy server. This means that the three-way handshake – […]
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 […]
Service pricing – Using AWS Wavelength Zones on Public 5G Networks
It is important to be aware of the pricing difference for AWS services when they are deployed to a Wavelength Zone versus a standard availability zone. The next figure shows an example of the difference for different EC2 instance types in us-east-1 (Northern Virginia region) and us-east-1-atl-1a (Atlanta Wavelength Zone): Figure 7.25 – On-demand pricing […]
Amazon Route53 for load balancing – Using AWS Wavelength Zones on Public 5G Networks
For non-HTTP(s) applications or AWS Wavelength Zones outside the US, it is possible to use Amazon Route53 weighted routing policies for load balancing (see Chapter 6). However, unlike using it in standard regions or AWS Local Zones, it is not possible to use the health check feature in the normal way. This is because the […]
Comparing AWS Wavelength deployments across global carriers – Using AWS Wavelength Zones on Public 5G Networks
AWS Wavelength is a series of individual partnerships with carriers around the world. An EC2 instance, or ECS/EKS container in an AWS Wavelength Zone, is specifically meant to service requests coming from mobile devices on that MNO’s network. SLAs for a given mobile device around latency, jitter, and similar network parameters are specific to each […]