The conversation

Lessons learnedExperience excerpt · English

I've worked for 2 large-ish firms in the past 3 years

… I've worked for 2 large-ish firms in the past 3 years. One huge telco, one "medium" telco (still 100s of people). BOTH had a team just for AWS IAM administration. Only for that one thing, because that was company-wide (and was regularly demonstrated to be a single point of failure). And they had AWS administrator teams, yes teams, for every department (even HR had one, though in the medium telco all management had a shared team, but the networking and development departments still had their own AWS teams, who, btw, also did IAM. The company-wide IAM team maintained an AWS IAM and some solution they'd bought that also worked for their windows domain and ticketing system (I hate you IBM remedy), and eqiupment ordering portal and ...) AND there were "devops" positions on every development team, and on the network engineering team, and even a small one for the building "technics" team. …

Original discussionAWS to bare metal two years later: Answering your questions about leaving AWS491 source comments · at import
2

What was this responding to?

Parent context · original excerpt

EN

You can't. That's the use case FOR AWS/GCP. Once the differential between having a in-house team and the AWS premium becomes positive is when you make the switch. A lot of the discussion here is that the cost of the in-house team is less than people think. For instance: at a former gig, we used a service in the EU that handled weekends, holidays and night time issues and escalated to our team as needed. It was pretty cheap, approximately $10K monthly fee for availability and hourly rate when there were any issues to be resolved. There were a few mornings I had an email with a post-mortem report and an invoice for a hundred euros or so. We came pretty close to 5 9's uptime but we didn't have to worry about SLA's or anything.

Full original

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 2

Direct replies available in this import. Original-language excerpts.

1O

Exactly. this is the margin aws trives from. they sell "you don't need a team"... which is true om your prototype and mvp phase. and you know when you grow you will have an ops team and maybe move out. but in the very long middle time... you will be supporting clients and sla etc, and will end up paying both aws AND an ops team without even realizing.

Full original
EN

Yeah, you need less admin, depending but not none. And AWS pushes you towards devops heavy solutions.

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.