51–60 of 93 posts
Earlier quoted context omitted.
Guys, please, try to be reasonable here. 150 miles is not an insert for Amazon. I'm not a general, but even I can see that 150 miles is military sense.
It’s probably 150 miles within an availability zone.
Seems a bit too tailored though - "To even make a bid, a provider must maintain a distance of at least 150 miles between its data centers, a prerequisite that only Amazon can currently meet. JEDI also asks for “32 GB of RAM”—the precise specification of Amazon’s services. (Microsoft, by contrast, offers only 28 GB, and Google provides 30 GB.) In places, JEDI echoes Amazon’s own language: It calls for a “ruggedized” s…
It sounds like the military wants what Amazon can provide, but is allowing other competitors to step up and give it a better deal. There are obvious reasons why a military customer would want distance between data centers and ruggedized storage, that's surely one of the reasons why Amazon has implemented them.
Seems a bit too tailored though - "To even make a bid, a provider must maintain a distance of at least 150 miles between its data centers, a prerequisite that only Amazon can currently meet. JEDI also asks for “32 GB of RAM”—the precise specification of Amazon’s services. (Microsoft, by contrast, offers only 28 GB, and Google provides 30 GB.) In places, JEDI echoes Amazon’s own language: It calls for a “ruggedized” s…
I have DoD clients currently doing app dev on new and replacement (for legacy) systems. This writers attempt at making the DoD contract look like a conspiracy is infuriating. The developer experience in the current data center ecosystem is toxic. The infrastructure and insecurity woes compound daily. I don’t care how much Bezos makes, he has a great product and DoD, nay the country, need this. GovCloud would be ice w…
The cottage industry around this specific contract is going to be massive. Whats really interesting though, is that, a huge swath of talent will be ineligeble to work on this as GovCloud/FedRamp requirements for US Citizen employees, physically located in the US to be able to access and work on any of these systems really does impose some limits on the pool. And while, regardless of how you look at this, it is dysopi…
That doesn't stop some DoD contractors from still subcontracting foreign nationals. Crazy what goes on.
Question: How do you vet a non-citizen for work on a DoD system? Let me give you a tiny example. Let's say you have a system for keeping track of jet parts. Super important stuff. What's to say a foreign agent couldn't make a subtle "mistake" that allows for misuse or misallocation of parts by not properly storing their flight history? Planes fail and fall out of the sky. This could totally happen (not saying it has although, again, the stories I hear JFC) and a competing state would be foolish not to try it.
Amazon being in line to win a large government contract while the President openly despises Amazon is actually a testament to proper government procurement. The real scandal would be if the President ordered Amazon to not be considered because of his personal beef with the Washington Post (and IMO general jealousy regarding Bezos who is actually as successful as Trump has always dreamed of being). tl;dr It is not a s…
TLDR: amazon knows people at dod, they decide to do business together, who cares?
Why would such a massively important backbone of US defense want to rely on only a single provider? It should be using all 3 of the major players (or others) and even some on premise stuff. This seems like a nightmare waiting to happen, and crony capitalism at its finest. The fact that Amazon says in the article that using fail overs to other providers is some hassle...is just amazing.
a) prevents you from using any of the custom features that many each service great (for instance lambda, aurora, dynamodb or in the case of google cloud, some of their ML tech). Might as well use on-prem if you’re not going to using AWS/Azure/GSuite feature on top of IaaS b) requires you to set up multiple alarms, logs, metrics, on different providers which can themselves be the source of bugs c) doesn’t provide you much more availability/redundancy them simply using multiple regions d)while this may give you long term negotiating power, you will likely just save more money with long term exclusive contracts.
The DOD will also likely never be 100% migrated to AWS and there will probably be more contracts