AWS to bare metal two years later: Answering your questions about leaving AWS

Re:AWS to bare metal two years later: Answering your questio... by ghaff on Wednesday October 29, 2025 @12:14PM (#45748899)

A lot of people forget that, when server virtualization was still gaining momentum in a lot of circles, it wasn't uncommon at less technically savvy customers--say a regional bank at the time--to be told that it might take 2 months to provision a new server.

[ Parent | on HN ]

Re:AWS to bare metal two years later: Answering your questio... by whstl on Wednesday October 29, 2025 @12:17PM (#45748943)

I don't think anyone is forgetting that in this thread, as there's dozens of answers mentioning this.

But as an example: It took about 3 months to provision an AWS server in a recent company I consulted for due to their own bureaucracy and ineptitude of the Ops team.

On the other hand, when I needed a few CI servers for a startup I worked at, I just collected them from AppleStore during lunch hour.

Now this above is what people are "forgetting" and don't want to listen to.

[ Parent | on HN ]

Re:AWS to bare metal two years later: Answering your questio... by maccard on Wednesday October 29, 2025 @04:56PM (#45752907)

For us the problem is every device that gets plugged into our network is disabled by default, IT need to enable the port and they'll only enable it on machines that they've imaged.

But because AWS isn't in the office, it's fine. We could probably use Hetzner or OVH, but then we have to go through procurement which is as much of as hassle as going through IT.

[ Parent | on HN ]

Re:AWS to bare metal two years later: Answering your questio... by whstl on Thursday October 30, 2025 @08:14AM (#45759169)

Now there's two dozen posts with the same example repeated.

[ Parent | on HN ]