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 […]
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 […]
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 […]
Migrating to the cloud and updating your infrastructure can be tricky. The simultaneous migration of interconnected applications can be challenging; thus, many choose not to entirely abandon their infrastructures in one shot. An incremental approach to lift-and-shift migrations was typical even before AWS Local Zones were introduced. Figure 6.5 – Migrating from VMware to EC2 […]
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 […]
AWS Outposts servers offer HA through the use of redundant power equipment that can be paired with dual customer-provided power sources for even greater resilience. Power is critical to any compute resource but network connectivity is also critical for Outposts deployments as management, monitoring, and service operations need connectivity to the anchor AZ. However, Outposts […]
Delivery and installation are performed through secure channels. Furthermore, any replacement parts are delivered through these same secure channels. Note that replacements are always provided in the event of failed hardware – no network switches or servers will be repaired after installation, only replaced. Using AWS Outposts Server AWS Outposts servers are designed in smaller […]
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 […]
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 […]
When an Outposts rack requires physical maintenance or hardware replacement, AWS works with the customer to schedule AWS personnel to come to the facility and replace the hardware. Customers can use the provided Nitro Security Key to cryptographically shred data according to NIST standards before returning it to AWS. Logical networking Now that we’ve covered […]
