An AWS Region is coming to France(allthingsdistributed.com)
allthingsdistributed.com
An AWS Region is coming to France
http://www.allthingsdistributed.com/2016/09/aws-announce-eu-france-region.html
69 comments
AWS in London is coming within months, so if latency to London is your concern, that's not an issue anymore.
https://aws.amazon.com/blogs/aws/coming-in-2017-new-aws-regi...
https://aws.amazon.com/blogs/aws/coming-in-2017-new-aws-regi...
For anyone using Virgin Media as their ISP, the Dublin DC will perform more predictably, if not faster, because of VM's "give preference to data originating inside the UK/Ireland and don't give two shits about anything else" attitude.
If you run a data heavy service, PoP inside the UK or Ireland is a must if you want to avoid throttling and heavy-handed traffic shapping.
If you run a data heavy service, PoP inside the UK or Ireland is a must if you want to avoid throttling and heavy-handed traffic shapping.
From London:
(To Frankfurt)
--- dynamodb.eu-central-1.amazonaws.com ping statistics ---
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 20.431/26.779/80.987/8.822 ms
(To Ireland) --- dynamodb.eu-west-1.amazonaws.com ping statistics --- 100 packets transmitted, 100 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 15.306/22.425/63.455/9.655 ms
To Softlayer Paris: --- speedtest.par01.softlayer.com ping statistics --- 100 packets transmitted, 100 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 12.082/16.196/54.741/7.652 ms
(To Ireland) --- dynamodb.eu-west-1.amazonaws.com ping statistics --- 100 packets transmitted, 100 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 15.306/22.425/63.455/9.655 ms
To Softlayer Paris: --- speedtest.par01.softlayer.com ping statistics --- 100 packets transmitted, 100 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 12.082/16.196/54.741/7.652 ms
I've found latency in the UK can be about a third lower than Ireland. I used Bytemark for testing in my recent book but Azure have UK regions now [0] and DO have had a London DC for a couple of years [1]. AWS UK is currently just "coming soon" [2] but Werner has said "end of 2016 (or early 2017)" [3].
[0] https://unop.uk/azure-eu-regions-naming-confusion
[1] https://www.digitalocean.com/company/blog/introducing-our-lo...
[2] https://aws.amazon.com/about-aws/global-infrastructure
[3] http://www.allthingsdistributed.com/2015/11/aws-announces-uk...
[0] https://unop.uk/azure-eu-regions-naming-confusion
[1] https://www.digitalocean.com/company/blog/introducing-our-lo...
[2] https://aws.amazon.com/about-aws/global-infrastructure
[3] http://www.allthingsdistributed.com/2015/11/aws-announces-uk...
> [0] https://unop.uk/azure-eu-regions-naming-confusion
I expect Microsoft are using the UN region names for Europe, where Britain are Ireland are part of Northern Europe.
https://en.wikipedia.org/wiki/United_Nations_geoscheme_for_E...
I expect Microsoft are using the UN region names for Europe, where Britain are Ireland are part of Northern Europe.
https://en.wikipedia.org/wiki/United_Nations_geoscheme_for_E...
Nice find! That probably explains it.
The UK names still aren't great, even if they sound reasonable in isolation (Cardiff - West, London - South). They have fixed the map though.
The UK names still aren't great, even if they sound reasonable in isolation (Cardiff - West, London - South). They have fixed the map though.
> Article states UK region "due in coming months". No location announced?
At the bottom of the English section it says it's London
The new European region, coupled with the existing AWS Regions in Dublin and Frankfurt, and a future one in London,
At the bottom of the English section it says it's London
The new European region, coupled with the existing AWS Regions in Dublin and Frankfurt, and a future one in London,
It's hardly surprising. Everything on the UK internet goes through London anyway. If you have a DC in Manchester and an end-user in Liverpool, the link normally goes Manchester - London - Liverpool.
It's not a great situation, having everything so centralised on London, but it's a small enough country that it doesn't have a huge effect on latency. It would make no sense for AWS to locate in a non-London region when everything would then have to be backhauled to London.
It's not a great situation, having everything so centralised on London, but it's a small enough country that it doesn't have a huge effect on latency. It would make no sense for AWS to locate in a non-London region when everything would then have to be backhauled to London.
A 10 year old PDF map [1] shows plenty of other fibre connections. Does everything really go through London?
Locating outside London would be a lot cheaper, for labour, land and power.
[1] http://www.globalcrossing.com/docs/fn/tanet-uk-map.pdf
Locating outside London would be a lot cheaper, for labour, land and power.
[1] http://www.globalcrossing.com/docs/fn/tanet-uk-map.pdf
There is fibre outside London, but most of the main end-user ISPs have just the one POP and it's normally in Docklands. Everything ends up going through there one way or another.
Not every decision is about cost minimisation. There's a resiliency motivation to place DCs in separate flood plains and separate power grids if possible. Whether AWS is following that, I cannot say.
We (I am part of the AWS team) pay a lot of attention to that; our "Overview of Security Practices" paper[1] says:
"Each availability zone is designed as an independent failure zone. This means that availability zones are physically separated within a typical metropolitan region and are located in lower risk flood plains (specific flood zone categorization varies by Region). In addition to discrete uninterruptable power supply (UPS) and onsite backup generation facilities, they are each fed via different grids from independent utilities to further reduce single points of failure. Availability zones are all redundantly connected to multiple tier-1 transit providers."
[1] https://d0.awsstatic.com/whitepapers/aws-security-whitepaper...
"Each availability zone is designed as an independent failure zone. This means that availability zones are physically separated within a typical metropolitan region and are located in lower risk flood plains (specific flood zone categorization varies by Region). In addition to discrete uninterruptable power supply (UPS) and onsite backup generation facilities, they are each fed via different grids from independent utilities to further reduce single points of failure. Availability zones are all redundantly connected to multiple tier-1 transit providers."
[1] https://d0.awsstatic.com/whitepapers/aws-security-whitepaper...
London does have food risk back in the 80's when I worked for British Telecom we moved our central London DC(next to London bridge station) out to Add to crickelwood for that reason.
Of course later on the IRA bombed the building next door to us - we survived ok the modems just rest them selves
Of course later on the IRA bombed the building next door to us - we survived ok the modems just rest them selves
I've always assumed that availability zones would not necessarily be in the same building or even site in a given region, but something I've wondered is what does the network look like between zones?
Does inter-AZ traffic traverse only fiber that you wholly own? Does AWS send traffic over some shared links in some cases? If only some cases, which cases?
Does inter-AZ traffic traverse only fiber that you wholly own? Does AWS send traffic over some shared links in some cases? If only some cases, which cases?
James Hamilton gives a good talk that goes over networking (and more). This is it from reinvent 2014.
https://m.youtube.com/watch?v=JIQETrFC_SQ
https://m.youtube.com/watch?v=JIQETrFC_SQ
This is great. I operate a French website targeted to French customers, this will improve latency compared to Ireland.
This might also allow for mixing critical server roles hosted in other Paris data centers with AWS.
I'm thinking about connecting a web server (in AWS) with a DB server (in another Paris DC) while keeping the latency at a low level.
This might also allow for mixing critical server roles hosted in other Paris data centers with AWS.
I'm thinking about connecting a web server (in AWS) with a DB server (in another Paris DC) while keeping the latency at a low level.
> (in another Paris DC)
For bonus points, choose the same DC that AWS is actually in http://www.equinix.com/locations/france-colocation/france-da...
For bonus points, choose the same DC that AWS is actually in http://www.equinix.com/locations/france-colocation/france-da...
Mmmm interesting.
I have servers there: http://www.iliad-datacenter.com/ in DC3.
What is the state of the temporary spy laws in France?
Shouldn't it at least be mentioned in the announcement that the french government can pretty much ask Amazon for any of your data without a warrant. Or is the situation better than a year ago?
EDIT: Warrant is apparently needed as noplay said.
Shouldn't it at least be mentioned in the announcement that the french government can pretty much ask Amazon for any of your data without a warrant. Or is the situation better than a year ago?
EDIT: Warrant is apparently needed as noplay said.
They need warrant to get access to your server. What they can do is to collect metadata in some points of the network, they don't need amazon to do that, because they target end users.
But it's probably not a good idea to host in France if you have not reason to do that. Like NSA, french secret service just don't care about laws. But if you target french customer that's good news you have one more alternative for hosting without trouble with regulation about data.
But it's probably not a good idea to host in France if you have not reason to do that. Like NSA, french secret service just don't care about laws. But if you target french customer that's good news you have one more alternative for hosting without trouble with regulation about data.
If you're referring to the current "state of emergency" (état d'urgence) it has been extended multiple times already since nov '15, and allows warrantless searches (perquisition administrative).
The last extension is effective since 2016-07-26 and is supposed to last 6 months.
The last extension is effective since 2016-07-26 and is supposed to last 6 months.
In France, we have some consideration toward power separation. Police and secret services can collect your data mostly without a warrant. Government can exceptionally ask the police some data, but if there are abuses, the judicial power will intervene.
I meant government as in government agencies, not strictly under the direct control of the actual group of humans making up the government.
I guess "government" interprets to different things in different countries, what I wrote above is a very american viewpoint.
In my country (SE), a member of government can be relieved of her duties if she even mentions that an agency should act in a certain way (as the government only should make up policies and not interfere in the daily businesses of the agencies).
https://en.wikipedia.org/wiki/Ministerstyre
I guess "government" interprets to different things in different countries, what I wrote above is a very american viewpoint.
In my country (SE), a member of government can be relieved of her duties if she even mentions that an agency should act in a certain way (as the government only should make up policies and not interfere in the daily businesses of the agencies).
https://en.wikipedia.org/wiki/Ministerstyre
Yeah in France separation is less clear. That's why warrant is not the problem if they want it they will get it anyway.
Still no further info on the London region since their announcement post[1] said:
> Today, I am excited to add the United Kingdom to that list! The AWS UK region will be our third in the European Union (EU), and we're shooting to have it ready by the end of 2016 (or early 2017). This region will provide even lower latency and strong data sovereignty to local users.
[1] http://www.allthingsdistributed.com/2015/11/aws-announces-uk...
> Today, I am excited to add the United Kingdom to that list! The AWS UK region will be our third in the European Union (EU), and we're shooting to have it ready by the end of 2016 (or early 2017). This region will provide even lower latency and strong data sovereignty to local users.
[1] http://www.allthingsdistributed.com/2015/11/aws-announces-uk...
AWS Re:Invent is coming up in early December; I wouldn't be surprised if they announced general availability by then.
Since UK is about to be outside of the EU it's likely this has been put on hold?
I don't know what the facts are but I'm guessing the UK accounts for a large slice of data currently being routed via Ireland, so it isn't going to be on hold for long?
No it's not on hold: https://aws.amazon.com/blogs/aws/coming-in-2017-new-aws-regi...
I know you can target Ireland as the API endpoint for SES, but in light of Brexit and all the issues still with Safe Harbour, hopefully having a UK offering will make me a lot happier with routing email sends (data wise).
Yes, they confirmed it here:
https://aws.amazon.com/blogs/aws/coming-in-2017-new-aws-regi...
> This will be the fourth AWS Region in Europe. We currently have two other Regions in Europe — EU (Ireland) and EU (Frankfurt) and an additional Region in the UK expected to launch in the coming months.
https://aws.amazon.com/blogs/aws/coming-in-2017-new-aws-regi...
> This will be the fourth AWS Region in Europe. We currently have two other Regions in Europe — EU (Ireland) and EU (Frankfurt) and an additional Region in the UK expected to launch in the coming months.
I do sincerely wished Amazon would have consider changing their AWS service management UI and workflow as well as epanding their servers around the globe.
Currently it is an incredibly inefficient design of a service management trying to do everything yet many are dependent for using it.
Currently it is an incredibly inefficient design of a service management trying to do everything yet many are dependent for using it.
If you're big enough that switching regions in the console is a regular pain, you're probably big enough to just automate stuff via the APIs.
This maybe a fact but not an excuse for poor user experience.
AWS initially launched API-only. At any significant scale, it's simply not intended to be managed via the console.
I found visualization very much helpful when complexity rises. APIs stays powerful but do not support a human admin for monitoring and server setups (including IAM users, Services, Tasks, Clusters, Launching EC2 instances, ECR setup for docker, AIM, Loadbalancing, Security groups, Roles etc all multiplied to X regions).
Again, if you're large enough to be in multiple regions, all of this should be configured via the APIs using a configuration management system of some sort.
Ansible, for example, can easily manage stuff like security groups (http://docs.ansible.com/ansible/ec2_group_module.html) , load balancing (http://docs.ansible.com/ansible/ec2_elb_lb_module.html), IAM users and roles (http://docs.ansible.com/ansible/iam_module.html), etc., and it does them in repeatable, auditable, version-controllable, self-documenting fashion.
Ansible, for example, can easily manage stuff like security groups (http://docs.ansible.com/ansible/ec2_group_module.html) , load balancing (http://docs.ansible.com/ansible/ec2_elb_lb_module.html), IAM users and roles (http://docs.ansible.com/ansible/iam_module.html), etc., and it does them in repeatable, auditable, version-controllable, self-documenting fashion.
" if you're large enough to be in multiple regions, all of this should be configured via the APIs"
Is the suggestion to recreate what Amazon Console has done (using APIs) in every large organisation using AWS because Amazon Console is not good enough?
Is the suggestion to recreate what Amazon Console has done (using APIs) in every large organisation using AWS because Amazon Console is not good enough?
No, treat your infrastructure as code. Define it programatically, version it, have a standard, automated process for recreating it.
If you're using AWS then Cloudformation (maybe with an abstraction like troposphere), will do what you need.
If you are pressing the big blue 'launch instance' button, you are doing it wrong.
If you're using AWS then Cloudformation (maybe with an abstraction like troposphere), will do what you need.
If you are pressing the big blue 'launch instance' button, you are doing it wrong.
"No, treat your infrastructure as code."
Agreed. Advantage is clear and understood.
My point here is: there exists something called 'Amazon Console'. I argue it is a good thing to have if done properly easing the service management as visualized management is more human friendly and APIs more computer friendly. If there exists a bad visualized service management (e.g. Amazon Console) it is the lack of skills of the humans developing it not because managing a vast complex clusters is easier through APIs/CLI and impossible/wrong via UI.
Agreed. Advantage is clear and understood.
My point here is: there exists something called 'Amazon Console'. I argue it is a good thing to have if done properly easing the service management as visualized management is more human friendly and APIs more computer friendly. If there exists a bad visualized service management (e.g. Amazon Console) it is the lack of skills of the humans developing it not because managing a vast complex clusters is easier through APIs/CLI and impossible/wrong via UI.
I'm not sure what a console that performs the current tasks and spans multiple regions at once would look like, or that it would make things feel simpler.
What's your suggestion for improving the UX?
What's your suggestion for improving the UX?
Extending the UX with "the current tasks and spans multiple regions at once" is definitely NOT the right way.
I believe the current sub-categorizing of services:
API Gateway, AppStream, AWS IoT, Certificate Manager, CloudFormation, CloudFront, CloudSearch, CloudTrail, CloudWatch, CodeCommit, CodeDeploy, CodePipeline, Cognito, Config, Data Pipeline, Device Farm, Direct Connect, Directory Service, DMS, DynamoDB, EC2, EC2 Container Service, Elastic Beanstalk, Elastic File System, Elastic Transcoder, ElastiCache, Elasticsearch Service, EMR, GameLift, Glacier, IAM, Inspector, Kinesis, Lambda, Machine Learning, Mobile Analytics, Mobile Hub, OpsWorks, RDS, Redshift, Route 53, S3, Service Catalog, SES, Snowball, SNS, SQS, Storage Gateway, SWF, Trusted Advisor, VPC, WAF, WorkDocs, WorkMail, WorkSpaces.
is not helpful and confusing for new users. This is because all the mentioned services are a mix of dependent (e.g. ECS depends on EC2), independent(e.g. IAM & EC2), security, services acting like plugins.
The documents for all of these services can be a sequel novel. If you have been with AWS since 2012 you may have gradually been updated by each service that was getting blindly added but for a new user or a startup aiming to setup something or test the scalability of their application ASAP it is a nightmare.
The other day I found out (in a hard way) that you cannot launch an EC2 instance with an AWS container agent from the default launch page but you need to go to the launch page via the document link which puts extra parameters in the url...
Having said all that I believe the improvement needs to be more fundamental than couple of bullet points.
I believe the current sub-categorizing of services:
API Gateway, AppStream, AWS IoT, Certificate Manager, CloudFormation, CloudFront, CloudSearch, CloudTrail, CloudWatch, CodeCommit, CodeDeploy, CodePipeline, Cognito, Config, Data Pipeline, Device Farm, Direct Connect, Directory Service, DMS, DynamoDB, EC2, EC2 Container Service, Elastic Beanstalk, Elastic File System, Elastic Transcoder, ElastiCache, Elasticsearch Service, EMR, GameLift, Glacier, IAM, Inspector, Kinesis, Lambda, Machine Learning, Mobile Analytics, Mobile Hub, OpsWorks, RDS, Redshift, Route 53, S3, Service Catalog, SES, Snowball, SNS, SQS, Storage Gateway, SWF, Trusted Advisor, VPC, WAF, WorkDocs, WorkMail, WorkSpaces.
is not helpful and confusing for new users. This is because all the mentioned services are a mix of dependent (e.g. ECS depends on EC2), independent(e.g. IAM & EC2), security, services acting like plugins.
The documents for all of these services can be a sequel novel. If you have been with AWS since 2012 you may have gradually been updated by each service that was getting blindly added but for a new user or a startup aiming to setup something or test the scalability of their application ASAP it is a nightmare.
The other day I found out (in a hard way) that you cannot launch an EC2 instance with an AWS container agent from the default launch page but you need to go to the launch page via the document link which puts extra parameters in the url...
Having said all that I believe the improvement needs to be more fundamental than couple of bullet points.
Do you have some specific feedback that I can share with the team? Which aspects of the console and the workflow are not working for you?
Its worth commenting that we here in Microsoft Azure team (our cloud platform) have data centers in 30 regions including UK, Germany, etc. https://azure.microsoft.com/en-us/regions/
Our platform is very mature now I wish more folks would give it a shot.
p.s. we also take EU people data privacy very seriously. https://www.thefastmode.com/technology-solutions/9077-micros...
Our platform is very mature now I wish more folks would give it a shot.
p.s. we also take EU people data privacy very seriously. https://www.thefastmode.com/technology-solutions/9077-micros...
> p.s. we also take EU people data privacy very seriously.
Hmmm. I find that very hard to believe.
MS is going to have to be _very_ good for a _long_ time to overcome firing the late Caspar Bowden (then MS' chief privacy adviser) for telling regional managers that the NSA can pwn their customers' data. https://twitter.com/casparbowden/status/542588420611379201
Hmmm. I find that very hard to believe.
MS is going to have to be _very_ good for a _long_ time to overcome firing the late Caspar Bowden (then MS' chief privacy adviser) for telling regional managers that the NSA can pwn their customers' data. https://twitter.com/casparbowden/status/542588420611379201
MS data centers are akin to AWS availability zones, not AWS regions.
I don't know how it currently compares with AWS but some time ago the disk IO was a lot slower, and the prices were way higher.
Does anyone know of recent comparisons?
So this is great however I have a very large concern.
In a U.S. AWS data center, I am very confident (right now) that my encryption keys and encrypted data will never be given out to any governmental agency. Even with a warrant, they can not access my data unencrypted.
What will Amazon do when the French government says hand us all of your keys or else...
As our data is all extremely sensitive financial information, we really can not even take that chance until we know.
Clarification: We send all data over HTTPS with AES 256 encryption. If authorities have a warrant for data, can we hand them the encrypted data and say the keys are in the U.S. and we can't give them to you?
In a U.S. AWS data center, I am very confident (right now) that my encryption keys and encrypted data will never be given out to any governmental agency. Even with a warrant, they can not access my data unencrypted.
What will Amazon do when the French government says hand us all of your keys or else...
As our data is all extremely sensitive financial information, we really can not even take that chance until we know.
Clarification: We send all data over HTTPS with AES 256 encryption. If authorities have a warrant for data, can we hand them the encrypted data and say the keys are in the U.S. and we can't give them to you?
Why are you:
1) Keeping keys to extremely sensitive financial data on a cloud server
2) Confident that the US government won't request this information through warrant or national security letter
3) Asking for advice about this on a message board?
1) Keeping keys to extremely sensitive financial data on a cloud server
2) Confident that the US government won't request this information through warrant or national security letter
3) Asking for advice about this on a message board?
1) They are in a key management service (not AWS). Highly unlikely somebody will get both access to the keys and the data together. They are also rotated periodically.
2) Well lately, I'm not. The Apple/FBI case was somewhat assuring. And I believe that to date, AWS has not handed over any data or keys without permission.
3) More theoretical advice about the new French region. What are the laws about privacy and how will that work. We just saw what Germany ruled on with WhatsApp. And really just asking the question because it needs to be asked. I don't actually expect an ultimate answer, just discussion about it.
2) Well lately, I'm not. The Apple/FBI case was somewhat assuring. And I believe that to date, AWS has not handed over any data or keys without permission.
3) More theoretical advice about the new French region. What are the laws about privacy and how will that work. We just saw what Germany ruled on with WhatsApp. And really just asking the question because it needs to be asked. I don't actually expect an ultimate answer, just discussion about it.
> 2) Well lately, I'm not. The Apple/FBI case was somewhat assuring. And I believe that to date, AWS has not handed over any data or keys without permission.
How would you know? The NSL would prevent Amazon from being able to say anything about it.
If you're that concerned about your security, you shouldn't be using a cloud provider.
How would you know? The NSL would prevent Amazon from being able to say anything about it.
If you're that concerned about your security, you shouldn't be using a cloud provider.
The Apple FBI case only happened because Apple was physically unable to hand over the data, since they had no access to it. If you have the keys, you have access to the data presumably, and you'll be giving it up once you're compelled to by the government (see Lavabit).
Would you feel better if NSA gets your data using a warrant signed by a secret court and gags Amazon using a NSL? Why do you think that US agencies can ask Lavabit to hand encryption keys, but the same can't happen with Amazon?
Comparing with the US I don't remember that France has any gag laws.
Comparing with the US I don't remember that France has any gag laws.
There is STILL no AWS region in Israel.
All Internet traffic in and out of Israel goes through three undersea cables connecting the country with Turkey, Greece, and Italy, and as such suffer from the kind of lag that happens when you're separated from your destination server by a couple thousand kilometers, usually more. There are no local cloud providers and the local entrepreneurial culture (which is MASSIVE for such a small country) either has to pay for cloud resources in Europe or has to pay for local non-cloud hosting, which is orders of magnitude more expensive and running on relatively ancient hardware (the local VPS shops have little incentive to upgrade).
Do we have to beg for Amazon to come here?!
All Internet traffic in and out of Israel goes through three undersea cables connecting the country with Turkey, Greece, and Italy, and as such suffer from the kind of lag that happens when you're separated from your destination server by a couple thousand kilometers, usually more. There are no local cloud providers and the local entrepreneurial culture (which is MASSIVE for such a small country) either has to pay for cloud resources in Europe or has to pay for local non-cloud hosting, which is orders of magnitude more expensive and running on relatively ancient hardware (the local VPS shops have little incentive to upgrade).
Do we have to beg for Amazon to come here?!
> the local entrepreneurial culture (which is MASSIVE for such a small country)
> (the local VPS shops have little incentive to upgrade)
> Do we have to beg for Amazon to come here?!
I'm surprised nobody has stepped in and built out their own cloud offering.
> (the local VPS shops have little incentive to upgrade)
> Do we have to beg for Amazon to come here?!
I'm surprised nobody has stepped in and built out their own cloud offering.
[deleted]
Market likely isn't big enough.
Amazon will come to Israel if they deem it profitable. They aren't exactly Google Fiber though, so I think they would avoid locating themselves in areas with poor connectivity options in the first place.
Not really, from AWS perspective it's about locating regions close to potential customers with $$$ and a desire for a local region. That desire might be due to regulatory requirements or poor connectivity to other regions.
To figure out where the next AWS regions are going, go down the wikipedia list of countries by GDP and try to think which large markets are not well served yet:
https://en.wikipedia.org/wiki/List_of_countries_by_GDP_(PPP)
In the Middle East there are several markets larger than Israel, and putting a region in Israel will probably not be tenable for Egypt, Saudi Arabia and the like.
There is no region in Africa...
Russia & Eastern Europe is not that well served...
https://en.wikipedia.org/wiki/List_of_countries_by_GDP_(PPP)
In the Middle East there are several markets larger than Israel, and putting a region in Israel will probably not be tenable for Egypt, Saudi Arabia and the like.
There is no region in Africa...
Russia & Eastern Europe is not that well served...
But most of the Middle East and Africa aren't wired up well enough to begin with let alone have strong entrepreneurial cultures to push for local cloud adoption. Israel has a booming startup culture, they just all must use European clouds if they decide to go with a cloud infrastructure (and the vast majority of them do).
Fast connections there are also few and far between in the Middle East and Africa. In Israel, LTE is ubiquitous in urban areas, most residences have either DOCSIS 3.0 or Fiber-to-the-curb, and a nationwide FTTH infrastructure is being built out currently. Domestic connections are great - the problem is just that almost nothing is hosted domestically.
Eastern Europe / Western Russia sounds like a good idea to me, although I'm not familiar with their local Internet topologies.
Fast connections there are also few and far between in the Middle East and Africa. In Israel, LTE is ubiquitous in urban areas, most residences have either DOCSIS 3.0 or Fiber-to-the-curb, and a nationwide FTTH infrastructure is being built out currently. Domestic connections are great - the problem is just that almost nothing is hosted domestically.
Eastern Europe / Western Russia sounds like a good idea to me, although I'm not familiar with their local Internet topologies.
Nothing in NZ either, 2500KM minimum for our data to go to get to any of the large cloud service providers in Sydney. Worth the lag though for the cost savings.
Well the population is very small, so you can have the culture but do you need such infrastructure?
Currently Ireland vs. Frankfurt is (more data needed of course)[2]:
And Frankfurt is about 100 miles further than Dublin.
But for a quick test, this looks like a good tool: http://www.cloudping.info/
Will be interested to test this once released to see UK / Paris vs. Dublin.
[1] Article states UK region "due in coming months". No location announced?
[2] Hitting ec2.eu-west-1.amazonaws.com vs. ec2.eu-central-1.amazonaws.com.