- Newest
- Most votes
- Most comments
It looks like you have already identified that the best options for you are either the local zone in Hamburg, or the AWS region in Frankfurt, both of which are about the same distance away.
AWS announced a local zone in Amsterdam more than two years ago https://press.aboutamazon.com/2022/2/aws-announces-global-expansion-of-aws-local-zones
Over the next two years, new AWS Local Zones will launch in Amsterdam, Athens, Auckland, Bangkok,
But according to the map here it's still marked as announced and not generally available https://aws.amazon.com/about-aws/global-infrastructure/localzones/locations/
You can register your interest in the Amsterdam local zone here https://pages.awscloud.com/local-zones-signup-form.html
There is currently an edge location in Amsterdam which you may be able to leverage https://aws.amazon.com/cloudfront/features/ but from how you describe your app I don't think this may be of much us to you.
Just to add to @Deekshitha_Urs comments
You can use a tools such as cloudping.info to determine which Region is nearest to you.
CloudFront is useful if this is a web application and there are static contents that can be cached.
Since this is latency sensitive, AWS Global Accelerator (AGA) is likely to be a better option to CloudFront. Traffic from AGA to your EC2 will go through AWS global network, and is usually faster.
AGA has a edge location in Amsterdam
Thanks, I'll use AGA and give a try to CloudFront.
- Deploy in EU (West) Region: Use the eu-west-1 region (Dublin) for closer proximity to Amsterdam and potentially lower latency.
- AWS Global Accelerator: Consider if you need global latency optimization.
- Amazon CloudFront: Use for content delivery to reduce latency.
eu-west-1 is not the closest region to Amsterdam, and if latency is the concern then it is not advisable to use this region. The regions in Frankfurt, Paris and London are all 100s of km closer than Dublin.
I developed an instance in Dublin, but the excessive distance from Amsterdam compared to Hamburg and Frankfurt makes it unusable for the purpose: the rtt ping is about 3 times greater. I will definitely use AGA and try Cloudflare. Thank you for your contribution
Relevant content
- asked 2 months ago
AWS OFFICIALUpdated 6 months ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Thank you all for your quick and complete answers to my "noob" question.
After a short test, I think I'll adopt AGA, which has given some noticeable improvements to latency and hop-tier to the Amsterdam edge. With some fine tuning on the subnets, I think it's a good solution while waiting for an AWS Region in Amsterdam.