Where AWS Route53 manipulates DNS responses, AWS Global Accelerator utilizes IP anycast to improve the availability and performance of applications. AWS Global Accelerator uses static anycast IP addresses to route user traffic to the optimal AWS endpoint based on proximity, health, and routing policies: Figure 6.22 – AWS Global Accelerator using one IP for three […]
This method of load balancing expects new connections to issue a fresh DNS query each time. Thus, it is prudent to consider the caching behavior of the client devices, as well as any DNS servers between them and Amazon Route53. By default, the Time To Live (TTL) of an A record in Amazon Route53 is […]
In addition to traffic distribution, Amazon Route53 health checks can be configured for each record to ensure traffic is only sent to healthy nodes. The next figure shows the health check configurations for our pair of WireGuard VPN servers in an AWS Local Zone: Figure 6.17 – Amazon Route53 health checks for two WireGuard VPN […]
So far, we’ve covered use cases that involve traffic to and from an existing on-premises data center. This section will review options to address situations where the traffic originates from various locations on the internet. Application Load Balancer When an Elastic Load Balancer is set up in an AWS Local Zone, it is done in […]
When using AWS Direct Connect to communicate with a region, AWS recommends the architecture shown in the following figure for production workloads to ensure maximum resilience: Figure 6.14 – AWS recommendation for maximum resilience with Direct Connect At the time of writing, only the AWS Local Zone in Los Angeles has more than one availability […]
In many cases, the data center a customer wants to reach an AWS Local Zone from is a self-built data center in its own building or perhaps in a colocation facility that does not happen to be an AWS Direct Connect Location. In cases such as this, an AWS Direct Connect Partner can offer what […]
The first step in the process is to navigate to the AWS Direct Connect page within the AWS Management Console and click Create Connection. Under Connection ordering type, select Classic. Next, choose the appropriate Location from the drop-down menu. Port speed options will vary depending upon the location chosen—only a subset will offer 100 gigabits […]
For use cases where resources in an AWS Local Zone need to communicate with resources in an on-premises data center in that same metro area, there are two basic approaches. The first is a physical connection via AWS Direct Connect and the second is a virtual connection via a VPN over the public internet. Both […]
Tools such as the AWS latency tester [https://aws-latency-test.com] help predict the latency benefits that a given device will experience when connecting through an AWS Local Zone vs a region: Figure 6.6 – AWS Local Zone latency test output This figure shows a small snippet of the output of this tool. It will geolocate the client’s […]
Outposts’ capacity is finite. As it is a physical installation, any expansion requires careful planning and potentially additional hardware. Customers need to monitor usage and predict future needs. The elasticity inherent to the cloud is present in Local Zones. While there might be soft limits, scaling resources is more straightforward, not requiring hardware interventions. Security […]
