As Amazon moves from day-1 company as it claimed once, to be the sales company like Oracle focusing on raking money, expect more outages to come, and longer to be resolved.

Amazon is burning and driving away the technical talent and knowledge knowing the vendor lock-in will keep bringing the sweet money. You will see more sales people hoovering around your c-suites and executives, while you will face even worse technical support, that seem not knowing what they are talking about, yet alone to fix the support issue you expect to be fixed easily.

Mark my words, and if you are putting your eggs in one basket, that basket is now too complex and too interdependent, and the people who built and knew those intricacies are driven away with RTOs, move to hubs. Eventually those services; all others (and also aws services themselves) heavily dependent on, might be more fragile than the public knows.

>You will see more sales people hoovering around your c-suites and executives, while you will face even worse technical support, that seem not knowing what they are talking about, yet alone to fix the support issue you expect to be fixed easily.

WILL see? We've been seeing this since 2019.

it will get worse

Do you have data suggesting AWS outages are more frequent and/or take longer to resolve?

This is a prediction, not a historical pattern to be observed now. Only future data can verify if this prediction was correct or not.

And has substantially changed in management in the last couple years. Have you read my first post?

That is why technical leaders’ role wouldn’t demand they not only gather data, but also report things like accurate operational, alternative, and scenario cost analysis; financial risks; vendor lock-in; etc.

However, as may be apparent just from that small set, it is not exactly something technical people often feel comfortable with doing. It is why at least in some organizations you get the friction of a business type interfacing with technical people in varying ways, but also not really getting along because they don’t understand each other and often there are barriers of openness.

I think business types vs technical types inherently have different perspectives especially for american companies. One has the "get it done at all costs" the other has "this can't be done since impossible/it will break this".

When a company moves from engineering/technical driven to sales/profit/stock price/shareholders satisfaction driven, once it was not possible to cut (technical) corners, now becomes the de facto. If you push the L7s/L8s out of the discussion room, who would definitely stop or veto circular dependencies, and replace with sir-yes-sir people, now you've successfully created short term KPI wins for the lofty chairs but with a burning fuse of catastrophic failures to come.

https://www.theregister.com/2025/10/20/aws_outage_amazon_bra... quoting from this

"And so, a quiet suspicion starts to circulate: where have the senior AWS engineers who've been to this dance before gone? And the answer increasingly is that they've left the building — taking decades of hard-won institutional knowledge about how AWS's systems work at scale right along with them."

...

"AWS has given increasing levels of detail, as is their tradition, when outages strike, and as new information comes to light. Reading through it, one really gets the sense that it took them 75 minutes to go from "things are breaking" to "we've narrowed it down to a single service endpoint, but are still researching," which is something of a bitter pill to swallow. To be clear: I've seen zero signs that this stems from a lack of transparency, and every indication that they legitimately did not know what was breaking for a patently absurd length of time."

....

"This is a tipping point moment. Increasingly, it seems that the talent who understood the deep failure modes is gone. The new, leaner, presumably less expensive teams lack the institutional knowledge needed to, if not prevent these outages in the first place, significantly reduce the time to detection and recovery. "

...

"I want to be very clear on one last point. This isn't about the technology being old. It's about the people maintaining it being new. If I had to guess what happens next, the market will forgive AWS this time, but the pattern will continue."

Sorry that bus (the culture mentioned in the article) has long left. The new company culture is more obedience.

I guess jassy is trying leave his mark in the company history. Removing Day 1 mentality and replacing it with Tick 1: every time stock market tickers tick is tick 1.

Squeeze the company to the last drop via stock price obsession

Any company CEO who lays off people openly or covertly because they hire too many people in the recent years. If the management decided to hire too many people they are the ones who are responsible for bad decision or bad management. Not the people who are hired by the decisions.

It's also not clear for extra storage, it seems you need to jump to the next plan to get a slightly larger capacity. This does not make sense since the biggest tier is business with 5TB cap. If you need more you fall under the enterprise "contact sales" tier.

Do I understand correctly; that humans ate first the bigger animals to extinction and moved to next smaller ? Isn't this counterintuitive? Bigger animals need better traps and (killing) tools while smaller ones can be catched by hand and can be choked ?

If I had to choose between a moose and a rabbit to hunt, I would go for the cute little bunny.

But don't take my choice as guidance, I grew up and lived in city.

A moose would feed your tribe a lot longer than a rabbit. Once you have established a solid harvesting process, it is much more efficient to sustain a population from larger animals.

Tribes, harvesting aren't those sound more like possible with modern social structures? I expect them to form in the latter part of the 1.5 million years period. In the graph from the tweet shows delicacy(!) was elephant around 1 million years ago.

Monkeys can be said to live in "tribes", and "harvesting" was just my polite euphemism for "bloody slaughter".

Each time a developer does something on a cloud platform, that moment the platform might start to profit for two reasons: vendor lock-in and accrued costs in the long term regardless of the unit cost.

Anything limitless/easiest has a higher hidden cost attached.

That's a valid approach but I am not sure soon there will be much non-smart device offerings possible to choose and purchase.

If google is trying to monopolize the hot mess by its power, then it's working, right?

Pip is to create document trail (so when they get sued they can show evidence ) and to force people into submission and resignation. So this way they can handle things quietly and dirty things kept undercover.