I setting up an AWS server for gulf countries and it is showing a few options for choosing near locations. So I want to know the nearest country location.
Thanks in advance
Update : With the opening of me-south-1 in Bahrain, it is the natural choice for workloads in the Gulf States.
AWS Mumbai(ap-south-1) would likely be the closest geographically. Frankfurt (eu-central-1) would probably be the second closest.
You can test speeds and latencies to various cloud regions/services with these tools:
speedtest
cloud ping
Related
We are running on aws where we run everything in 1 region and use AZ's for our services. So if a AZ failed we would still be "up" and servicing our customers.
From reading the Reliability Pillar of the AWS Well-Architected documentation, this would suggest that this is enough to do in the case of a failure:
Unless you require a multi-region strategy, we advise you to meet your
recovery objectives in AWS using multiple Availability Zones within an
AWS Region.
A see tools out there like Cloud Endure and Druva CloudRange, but they seem like more for on premise or other cloud providers migrating or recovering on aws.
My question is, it is hard to definitively find, but it appears regions never go down, maybe services within a AZ or the AZ goes down, so if you are using AZ's for your applications and databases and doing backups to s3(Cross-Region replication) is this enough for DR?
Regions may not go down but they can become functionally unusable. There was an outage of eu-west-2a about 3 months ago that rendered large parts of eu-west-2 more-or-less unusable.
If you want redundancy, you should be mirroring infra to at least one other region.
So, as the question title says,
How should we architect the solution using AWS ?
Do we need to consider the region first assuming we might use all the features in future or stick with a region which is near and migrate to other regions for additional service,when needed.
How generally it is decided ?
The cost is fairly negligible when looking at various services pricing between regions, but obviously worth noting if you're on a very tight budget.
Regarding availability most commonly will services be available day 1 in the following regions:
us-east-1
us-west-1
eu-west-1
You generally find that within a few weeks or months that services will be rolled out to other regions, with the exception of the China and Govcloud regions which can see a more significant delay.
New regions are generally deployed with a core set of services such as EC2, S3, RDS etc but after launch will start to add the remaining services there.
If your application is client facing (a client directly interacts with the application, over either a web browser or service API) then I believe geographical location can be more important to a degree than the pricing. Delivering as best an experience to the client in my opinion is more beneficial for example us-east-1 might be cheaper but your clients based in europe.
If you want the cutting edge the regions listed above will almost always be current. Obviously you need to weigh all of these factors and decide based on what is most important for your usecase.
What is the best region for my users?
Region A is closer but there is no network path to it. Does region B is the best choice for me?
Edit:
This for voice over app.
The image source:
https://cloud.withgoogle.com/infrastructure/
Using gcping helped in choosing the latency for my users.
As mentioned in the previous comment the closer the region to your users they will experience less latency, however they are certain factors that are outside of Google control such as the internet speed of your users.
Follow GCP best practices for region selection which is summarized in the following:
Latency
Pricing
Colocation with other Google Cloud services
Machine-type availability
Resource quotas
Website slow response slow from some locations
I have a web server hosted in AWS Oregon region.
Our customer are accessing this website from a different part of the world (mostly from US, UK, and Dubai)
static assets are already on the AWS CloudFront
Now a day most of the customer from Dubai and UK are complaining that our web site is very slow but in the same time, we tried to access the website from the USA and other location but its fast.
what cloud be the best solution to make the site fast for all the customer in different locations.
web server is under ELB and we are using the SSL (ACM) certificate on the ELB for https.
Please suggest me the best solution. what about the Route53 latency bases routing .. will this work for my case.
In AWS you have a lot of regions. Many of them closer to your costumers. So, why not replicate the server to a closer region to match your costumers location. It's a looong way from Oregon to UK and Dubai.
EDIT:
shahid: "so your saying we have to setup to on web server on every region.whihc will cost us a lot more."
#shahid it's not in all aws regions, maybe just one it's enough for your problem. For your example (uk and dubai) , you can set an instance in France or London that are a lot closer than Oregon. This is what it's cloud. And this is why cloud was created. Since you already have the assets in cloud front you have to do the same with servers, and the way to do that is to clone the instance to the closest region. Without this solution you are going back to the old times (one server for all the world) = no cloud = large traveling times
EDIT2:
you can try use some tool like pingdom to check the differences response times across the world. With this you can check and verify that the connection is a lot faster from Oregon that was from UK and Dubai. You will also see the response times from cloudfront, to check that it's working as it should
New to both these technologies.I am trying to do the below steps
1)Install Kong with aws marketplace
I simply clicked on installation on getkong.org
then selected AWS marketplace
2) I am in UK.
So selected region as Ireland
since I have not got any other region to select from.
Then clicked manual launch
I opened ec2 management console
selected free tier
t2.micro
I gave my windows IP and created security groups and instructed but i am getting error
The instance configuration for this AWS Marketplace product is not supported. Please see http://aws.amazon.com/marketplace/pp?sku=8enaazwzxnn2uypvc4p8u39da for more information about supported instance types, regions, and operating systems.
t2.micro does not appear in the pricing options for this Marketplace offering (it does for other Marketpace images), this leads me to suspect t2.micro isn't supported.
We know from experience that Cassandra may struggle being run on low memory 2 gig machines
I suspect Mashape are trying to prevent you hitting complicated tuning issues (although I cannot see any docs to back this up).
Perhaps start with an M4 Large which is one of the "smallest", cheapest yet memory optimised options for experimentation.
The list of Kong supported ec2 instances for Ireland appear as: