3 ms·
You still need headcount to manage systems on AWS. And not really fewer then if you would run them locally. Source: managed systems locally, am now managing sy
by steve1977 4y ago
You still need headcount to manage systems on AWS. And not really fewer then if you would run them locally.
Source: managed systems locally, am now managing systems on AWS
- mlnj 4y agoSurely the cloud managed solution reduces the amount of custom magic that I have to put into place to keep things running. Everything is standardized & documented. There is a huge community to turn to if help is needed. And very less work is required if I get hit by a bus and someone else is now the owner of the huge system that I previously owned.
- endisneigh 4y agobut you can run kubernetes on bare metal
- steve1977 4y agoIt is standardized and documented if you DO document it and properly use IaC like CloudFormation or Terraform. But you can absolutely have people do ad-hoc changes in AWS that are not gonna be reproducible. Also, all of your points apply to non-cloud systems too.
- bfeynman 4y agoif you think you need more headcount to do things on cloud you're doing it wrong. Just the identity setup alone needs multiple people, and that's almost a full time job for them. On cloud you don't have to worry about that at all, and it comes with full auditibility and compliance.
- steve1977 4y agoYeah that’s the sales pitch. As soon as reality sets in and you need to integrate with an existing identity service for example, things can get pretty complex quickly. AWS & Co. use cases always look nice on paper, in reality it’s often not as easy as advertised.
- ReflectedImage 4y agoCloud requires a giant team of people working on cost management for any none trivial project. You ain't saving headcount.