4 ms·
Other possible funny (but probably happened somewhere else) scenarios: It doesn't rely on him running it, it just runs under his UID. A widely distributed aut
by paranoidrobot 5y ago
Other possible funny (but probably happened somewhere else) scenarios:
It doesn't rely on him running it, it just runs under his UID.
A widely distributed authentication/security process does an internal healthcheck by looking up 'jbezos' on the datastore. A few hours ago someone disabled the jbezos user.
- nodesocket 5y agoHonestly this explanation is not that far fetched at all, in fact plausible.
- grogenaut 5y agonah a long time ago they moved everything to run as 'nobody' and that was before the move off of those systems and onto things like ECS. fun fact jeff's employee id is like 72 or something while still being the lowest as they didn't reset the oracle sequence once they got that system working after testing but before making his user.
- paranoidrobot 5y agoI know it's unlikely, but I've grown (even more) sceptical over the years. I've stopped being surprised when I encounter some configuration file somewhere with a comment: "TODO: Fix this later" and it turns out more than half the business relies on that thing being configured that way. Even at companies who do have the money and technical resources to do things right, things get forgotten, or pushed back on. So, while these are problems that are unlikely, I'm sure I'm not the only one wondering... "Did they have something dumb like this, too?"
- paxys 5y agoWould be a fun story but Bezos is still the executive chairman of Amazon, so his user account will be left very much intact.
- paranoidrobot 5y agoOk, so the account still exists, but it's now in a different OU and so the healthcheck that looks for it in the Office of the CEO ou fails... Again, a joke, but I've seen stuff fail in other dumb ways because of some assumptions that were made about things that never change (until the day they do).