421–430 of 468 posts
I think this is due to the data residency requirements in UAE. I'm working with a client in the health space and the government requirements requires me to store data only in UAE! Tried with AWS but they were not allowing any new instances and I had to go with Azure.
You can always selfhost
I think this is due to the data residency requirements in UAE. I'm working with a client in the health space and the government requirements requires me to store data only in UAE! Tried with AWS but they were not allowing any new instances and I had to go with Azure.
Check if the requirement is "only in the uae" or has to have the primary copy in the UAE
Earlier quoted context omitted.
> the government requirements requires me to store data only in UAE!
... but not only in an Azure datacenter! (The obvious option here might be an encrypted backup on some hard drives in a safe in a local office.)
I don't like Oracle. GCP has no servers in UAE. All other options were by local providers with not so friendly budget options
Earlier quoted context omitted.
Of course not. The surprising thing is that multiple availability zones were bombed simultaneously. And to my knowledge, they haven’t even yet said 2+ AZs were compromised.
Turns out that "availability zones" in cloud parlance seem to have nothing to do with geographical availability. Apparently they're logical splits and are more about billing than anything.
> https://docs.aws.amazon.com/whitepapers/latest/aws-fault-iso...
They are far enough apart that tornados, floods, and fires cannot simultaneously impact multiple.
Earlier quoted context omitted.
1. This wasn’t a strike on a single data center, it was strikes on many data centers. 2. Since that interview, AWS has started selling versions of their storage that isn’t redundant. It is not surprising that when AWS sells non-redundant storage that some data is not recoverable.
> This wasn’t a strike on a single data center, it was strikes on many data centers. He didn't say "but if you hit many data centres then there is a problem". The premise was if you hit data centre, user won't notice, without caveat that there is a limit.
11.3 Force Majeure. Except for payment obligations, neither party nor any of their affiliates will be liable for any delay or failure to perform any obligation under this Agreement where the delay or failure results from any cause beyond its reasonable control, including acts of God, labor disputes or other industrial disturbances, electrical or power outages, utilities or other telecommunications failures, earthquak…
> including acts of God Serious question: how do we know something is or isn't an act of god?
I wonder if they'll start adding an underground bunker to new data centers so you can put an S3 replica there?
It's more likely the entire data centre (not just backups) would need to be built underground (or cut and cover) at enormous expense. A price that perhaps for certain data sovereignty reasons the government of Bahrain (or companies in Bahrain requiring it) would be happy to pay?
Another way to do things on the cheap could be small-scale "covert hosting". Buy an apartment or house, maintain it to give an outside appearance of being an apartment or house, but inside it has a few racks of IT equipment. This has been done in the past for telephone exchanges in some countries, not for security reasons, but rather to hide an ugly bit of infrastructure that due to technology limitations of the time had to be located deep within a residential neighbourhood.
Earlier quoted context omitted.
Turns out that "availability zones" in cloud parlance seem to have nothing to do with geographical availability. Apparently they're logical splits and are more about billing than anything.
> An Availability Zone is one or more discrete data centers with separate and redundant power infrastructure, networking, and connectivity in an AWS Region. Availability Zones in a Region are meaningfully distant from each other, up to 60 miles (~100 km) to prevent correlated failures, but close enough to use synchronous replication with single-digit millisecond latency. > https://docs.aws.amazon.com/whitepapers/late…
I think this is due to the data residency requirements in UAE. I'm working with a client in the health space and the government requirements requires me to store data only in UAE! Tried with AWS but they were not allowing any new instances and I had to go with Azure.
Hi, I'm from the future. You might want to consider storing the data somewhere besides an Azure datacenter in the UAE.