4 ms·
That's not how the government engages with AWS and other vendors. Even though the rest of the world sees it as one big entity, they engage as if they're thousa
by count 5y ago
That's not how the government engages with AWS and other vendors. Even though the rest of the world sees it as one big entity, they engage as if they're thousands of smaller entities.
They generally get access to AWS through resellers, not direct, and from what I've seen, get a pretty substantial pass through reseller discount.
And finally, having seen USDS work, I'm fully willing to believe this is hosted in a basic AWS account they're paying for with a credit card that's on it's own stand alone setup. Rapid launch, standup, and fielding an independent thing generally doesn't play well with working inside those big contract/managed environments. I'd be surprised if the USPS was doing anything here but providing DNS and the address API on the backend.
- katzgrau 5y agoI definitely agree that the government as a whole isn't the end client - it's, of course, some sub org. But with the SLA and support requirements probably involved, I definitely don't see this running on a basic account.
- count 5y agoHaving spent uh, 11? years working with AWS for gov entities, I would actually be impressed if they had bothered to turn on support. I also assume, given the nature of the activity involved, that AWS had their solutions team there gratis making sure to remember to request limit increases and stuff.