3 ms·

I did not mean to imply that GovCloud was a contract. I though it was the exclusive provider of isolated cloud services. I didn't realize Azure had its Governme

I did not mean to imply that GovCloud was a contract. I though it was the exclusive provider of isolated cloud services. I didn't realize Azure had its Government region. Glad that exists, I want to see that competition. However FedRAMP is not relevant to what I was trying to say. My understanding is government itself directly uses just the AWS and now Azure isolated regions. What I was meaning to say was for the DoD, which I though was exclusively under AWS GovCloud, and AWS C2S, rather than the whole government. They could certainly be using Azure Government though. I am glad to know there is more competition than I though. Thanks.

dragonwriter 6y ago
> My understanding is government itself directly uses just the AWS and now Azure isolated regions. This is not true, at least based on the discussions I've been involved in with AWS reps (while my employer is a state government entity, how the feds use AWS has frequently come up.) There are US Government customers without the requirements that are only provided on the isolated regions that use the commercial offerings that have the appropriate guarantees for their data, and there are non-federal customers that use the isolated government regions for data which has the higher-level federal requirements that require those guarantees. FedRAMP isn't the only force here, but it's a key requirement that drives the choice. (Also, GovCloud was cleared for some requirements before commercial offerings, so some customers, including some federal ones, are currently on GovCloud with workloads that could be served on the commercial regions now.)