AWS GuardDuty – the Good, the Bad, and the Ugly

Re:AWS GuardDuty – the Good, the Bad, and the Ugly by marcinzm on Monday August 15, 2022 @09:07AM (#32469174)

I actually remember the old days and no bloody thank you. Sometimes you got arcana processes managed by barely technical sysadmins so it took you 5 months to get a VM and 2 months to reimage it if you broke it. Other times you got a free for all where every engineer configures an insecure never updated server that eventually gets hacked. Then you get paged at 2am when the thing explodes and get to spend two days rebuilding it. Especially fun when you didn't build it but simply inherited a magic undocumented machine from someone who left.

Personally I care more about my enjoyment of my day to day job than saving the company a tiny bit of money that they'll never give me.

[ Parent | on HN ]

Re:AWS GuardDuty – the Good, the Bad, and the Ugly by Jensson on Monday August 15, 2022 @11:04AM (#32470595)

Depends on the skill of the employees. If you have mostly juniors and people who don't care then AWS is a godsend. If you mostly hire capable seniors to lead and ambitious juniors to follow then you can run things the old way just fine.

My first job had only incompetent seniors that I had to explain SQL query performance to etc. I left very quickly since I realized I wouldn't learn much there. I can see such places benefiting greatly from AWS services.

[ Parent | on HN ]

Re:AWS GuardDuty – the Good, the Bad, and the Ugly by marcinzm on Monday August 15, 2022 @11:20AM (#32470828)

>If you mostly hire capable seniors to lead and ambitious juniors to follow then you can run things the old way just fine.

Or you can run them even better on AWS assuming you had the same level of competence except in cloud deployments. Granted they'd probably pick a more specialized cloud platform than AWS for the specific problems and scale of the team.

[ Parent | on HN ]