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 […]
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 […]
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 […]
While there are many use cases for AWS Local Zones, the drivers behind all of them boil down to three things. Reduced latency In today’s digital landscape, many tasks, including medical image processing, real-time gaming, telco virtualization, and enterprise transactions, necessitate fast access to compute power with minimal lag. Figure 6.2 – Customers in Texas […]
Amazon EBS volumes are not supported on Outposts servers; only instance store volumes are available. Similar to the in-region instance store, the instance store data persists after a reboot but not an instance termination. This means customers must use either stateless configurations or must back up instance data to a persistent destination such as Amazon […]
Outposts servers require two physical connections to perform properly and the cables needed for this connectivity are provided to customers with their Outposts server. The two connections are used to segment traffic according to traffic class and are not intended for redundancy. These connections are not required to be on a common network. The cable […]
ECS is a fully managed container orchestration service that simplifies the deployment, management, and scaling of containerized applications. Customers can launch non-Fargate versions of Amazon ECS within an AWS Outposts Rack deployment for full-scale container orchestration: Figure 5.16 – Launching an ECS cluster within a deployment by selecting an Outposts subnet The supplemental services of […]
RDS is a managed service that makes it simple to set up, operate, and scale databases in the cloud. The following database engines are available within an AWS Outposts Rack deployment: RDS for SQL Server RDS for PostgreSQL RDS for MySQL These databases have the advantage of being close to on-premises applications that require low […]
AWS Outposts Rack deployments can host the following instance types: M5/M5d for general-purpose workloads C5/C5d for compute-intensive workloads R5/R5d for memory-optimized workloads G4dn for graphics-optimized workloads I3en for I/O optimized workloads: Figure 5.11 – Deploying an EC2 instance to a subnet within an Outposts deployment AWS has plans to begin offering EC2 VT1 instances for […]
A common reason customers deploy AWS Outposts is because they have something in their on-premises data center, such as a database, and the application has very tight latency or jitter requirements. It wouldn’t do much good if an EC2 instance on an AWS Outposts instance had to route back over the service link to get […]
