我如何确定哪个 AWS 位置最适合为来自特定区域的客户提供服务? [英] How could I determine which AWS location is best for serving customers from a particular region?

问题描述

AWS 有多个位置供存储和 EC2 实例以不同的价格运行.我如何确定哪个位置最适合特定区域.它是直观的(靠近您的服务区域是最好的)还是有任何可靠性问题(特定的 AWS 位置比其他位置面临更多的中断).是否有任何数据可用于做出此类决定?

AWS has several locations for storage and EC2 instances to run upon with different pricing. How could I determine which location is best for a particular region. Is it intuitive (closer to your serving region is the best) or are there any reliability concerns (particular AWS location facing more outages than others). Is there any data available for making such decision?

我正在开发一个主要面向印度客户的应用程序.所以，我正在考虑选择新加坡或东京.

I am developing an application that is mainly targeted towards Indian customers. So, I am considering Singapore or Tokyo as an option.

推荐答案

为自定义使用确定最低延迟的 AWS 位置

来自 TurnKey Linux 的聪明和创新人士最近开源了他们的问题解决方案，请参阅 AWS 区域数据中心映射在 GitHub 上:

Determining lowest latency AWS location for custom usage

The smart and innovative folks from TurnKey Linux recently open sourced their solution to your problem, see AWS Regional Data Centers mapping on GitHub:

该项目用于生成索引(和视觉地图)参考)由 TurnKey Hub 用来找到最近的 AWS 数据中心对于用户.[强调我的]

This project is used to generate the indexes (and visual map for reference) used by the TurnKey Hub to find the closest AWS data center for a user. [emphasis mine]

使用的算法在使用GeoIP和索引查找最近的数据中心有更详细的说明 以及后续文章 使用 GeoIP 和索引查找最近的 APT 包存档.

The algorithm in use is further detailed in Finding the closest data center using GeoIP and indexing as well as the follow up post Finding the closest APT package archive using GeoIP and indexing.

虽然有点噱头，但可视化非常酷，并且证实了这一点.说明了乔什已经提到的乍一看令人惊讶的事实的原因，即澳大利亚的用户目前倾向于通过以下方式获得更好的延迟美国西部(北加州/us-west-1)而不是亚太地区(新加坡/ap-southeast-1).(提示:检查右下角的Future Cables 表明这可能会发生变化，详情请参阅Greg 的电缆地图，这表明澳大利亚可能会在未来几年内在两个 AWS 站点之间跳跃延迟；)

While a bit of a gimmick, the visualization is seriously cool and confirms resp. illustrates the reason for the at first sight surprising fact Josh mentioned already, namely that users in Australia currently tend to get better latency via the US West (Northern California / us-west-1) rather than the Asia Pacific (Singapore / ap-southeast-1) region. (Tip: checking Future Cables at the bottom right corner reveals this is likely going to change, which is further detailed in Greg's Cable Map, which indicates Australia might jump between both AWS locations latency wise in the years to come ;)

与此同时，AWS 提供了一张有用的地图，说明了他们的全球基础设施，以便进行快速评估，以及相应的详细信息，例如可用区和 API 端点的数量.

Meanwhile AWS is providing a helpful map illustrating their Global Infrastructure for a quick assessment, alongside respective details like e.g. number of availability zones and the API endpoint.

更重要的是，AWS 刚刚宣布了地理 DNS 支持 Jahufar 已经提到，请参阅介绍性帖子 基于多区域延迟的路由现在可用于 AWS，它正在提供支持 Amazon CloudFront 的相同基于延迟的路由技术 致 Amazon EC2 的用户，Elastic Load Balancing 等.

More importantly though, AWS has just announced the geographic DNS support Jahufar mentioned already, see the introductory post Multi-Region Latency Based Routing now Available for AWS, which is making available the same latency based routing technology that powers Amazon CloudFront to users of Amazon EC2, Elastic Load Balancing, and more.

因此，如果您的环境已经由 Auto Scaling EC2 实例架构组成，只需应用这种基于延迟的路由即可自动解决您的问题.

So in case your environment is comprised of an Auto Scaling EC2 Instances architecture already, simply applying this latency based routing should solve your problem automatically.

虽然该用例显然针对产生多个 AWS 区域的产品，但围绕基于延迟的路由和加权循环记录集的复杂功能也可能让您自己更轻松地确定所需的信息.

While the use case obviously targets offerings spawning multiple AWS regions, the sophisticated features around Latency Based Routing and Weighted Round Robin Record Sets might allow you to determine the desired information more easily yourself as well.

这篇关于我如何确定哪个 AWS 位置最适合为来自特定区域的客户提供服务?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！