The most common customer use cases are as follows: You can leverage Local Zones when you want to bring AWS resources close to your end-users or on-premises locations, and Direct Connect to achieve low latency, private, and dedicated connectivity between resources in AWS and on-premises workloads. Finally, we’ll review some architecture considerations when building the architectures described. After that, we will discuss the different reference architectures that you can have when connecting your on-premises locations and Local Zones using Direct Connect. First, it will cover common use cases that we’ve seen in our customers, and we’ll discuss how certain industries can benefit from the low latency, private, and dedicated connectivity with Local Zones using Direct Connect. This post will provide a deep dive into the relation between Local Zones and Direct Connect. With this announcement, network traffic takes the shortest path between Direct Connect locations and Local Zones, both for current and future ones. This new routing behavior reduces the distance that network traffic must travel, thereby decreasing latency and helping make your applications more responsive. This translated into an increased latency when you wanted a private and dedicated connection between your on-premises locations and Local Zones. Prior to this announcement, connectivity from a Direct Connect location to a workload running in a Local Zone (except for the Los Angeles one) would flow through the parent AWS Region of that specific Local Zone. In June 2022, AWS announced AWS Direct Connect support for all AWS Local Zones. This blog will focus on the second option. However, if you want private access, then you can use either a VPN or AWS Direct Connect. You can provide access through the public Internet, so employees and end users can use public IPs to access the applications. This means that you can deliver single-digit millisecond latency applications to your end-users in more locations.Īccessing applications on a Local Zone is similar to how you would do it in an AWS Region. As of November 2022, AWS has expanded Local Zones to 21 metropolitan areas, and announced plans to launch in 30 metros across 25 countries globally. Local Zones extend the capabilities of an AWS Region – what we called “parent” AWS Region. As a refresher, AWS Local Zones are a type of infrastructure deployment that place compute, storage, database, and other AWS services close to large population, industry, and IT locations. In December 2019, we announced our first Local Zone in Los Angeles.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |