我怎么能确定哪个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.
推荐答案
智能和创新的人从 Linux的TurnKey的最近开源的解决问题的方法，请参阅的AWS区域数据中心的映射：
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的为找到最近的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.
虽然有点噱头，在可视化是认真冷静和确认RESP的。说明了href="http://stackoverflow.com/a/6340130/45773">提到已，即用户在澳洲目前倾向于通过获得更好的潜伏期一见钟情令人惊讶的事实乔什
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刚刚宣布Jahufar 提到已经地理DNS支持，看到介绍后<一href="http://aws.typepad.com/aws/2012/03/latency-based-multi-region-routing-now-available-for-aws.html">Multi-Region延迟路由现在可用于AWS ，其中的是使现有的延迟相同的路由技术力量亚马逊的CloudFront的，以亚马逊EC2 ，用户弹性负载平衡，等等。的
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.
所以，如果您的环境是由一个自动缩放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屋！
