3 ms·

Was about to make this exact comment. Endless forms to fill out to move a network cable. Buuuut at my current workplace I am starting to see some slowdowns in

by zxcmx 9y ago

Was about to make this exact comment. Endless forms to fill out to move a network cable. Buuuut at my current workplace I am starting to see some slowdowns in doing AWS stuff as "departments" get more involved. Like the "cloud team" does the account but networks must provision the VPC, and there's a "gateway review board" that gets involved if you define a new network egress or ingress etc etc. I feel like many of the early advantages of cloud in enterprise are going to get eroded as the paper pushers catch on and "add value by defining process".

jimjimjim 9y ago
this. and also in these days of data breaches where the sensitive data was just lying around on open s3, more are more places require approval from above before adding anything to aws.
gaius 9y ago
Like the "cloud team" does the account but networks must provision the VPC, and there's a "gateway review board" that gets involved Yes, this is totally antithetical to modern working practices such as "DevOps" At that place e.g. the VM team could provision you a VM (eventually) but they couldn't do you a login on it, that was some other team. But you couldn't raise the paperwork against that team until the VM was created, so everything proceeded serially, and each step at a glacial pace. The time ratio between them and Azure or AWS is literally under one minute for every month!
- HighPlainsDrftr 9y ago
  It is - but the company probably is trying to solve a problem of past mistakes. I can only speculate, but at one point, someone must have munged a network acl and created an outage. Now all network acl's need to be reviewed before being added. Maybe someone toasted VPC peering. Or their was a private VPC full of sensitive data that all of a sudden was publically available. There was an old saying that 80% of outages were caused by humans. But there is more to account for than that. For example: - Certifications that the org has obtained - Contracts that the org has signed with customers - Compliance with laws and regulations (and international) - Insurance requirements It can add up in a hurry and can slow an org down quickly. It would be nice if an org could review all of its failures every few years and drop nearly all of its processes and procedures and start out fresh again - vowing to build around the failures of the past.
  - gaius 9y ago
    It would be nice if an org could review all of its failures every few years and drop nearly all of its processes and procedures and start out fresh again - vowing to build around the failures of the past Indeed. That IT department is learning a lesson of what happens when your end users discover cloud providers and come into the office and tell their management how quick and easy it is. Managers don't know or care about the past - they only know that what should take minutes is taking months. If that department had been able to turn around a VM request in a day or two - not unreasonable - they would have been safe. Now they are being asked questions for which they have no good answers, such as, what exactly do all of you do all day?

by zxcmx 9y ago

jimjimjim 9y ago

this. and also in these days of data breaches where the sensitive data was just lying around on open s3, more are more places require approval from above before adding anything to aws.

gaius 9y ago

Like the "cloud team" does the account but networks must provision the VPC, and there's a "gateway review board" that gets involved Yes, this is totally antithetical to modern working practices such as "DevOps" At that place e.g. the VM team could provision you a VM (eventually) but they couldn't do you a login on it, that was some other team. But you couldn't raise the paperwork against that team until the VM was created, so everything proceeded serially, and each step at a glacial pace. The time ratio between them and Azure or AWS is literally under one minute for every month!

HighPlainsDrftr 9y ago
It is - but the company probably is trying to solve a problem of past mistakes. I can only speculate, but at one point, someone must have munged a network acl and created an outage. Now all network acl's need to be reviewed before being added. Maybe someone toasted VPC peering. Or their was a private VPC full of sensitive data that all of a sudden was publically available. There was an old saying that 80% of outages were caused by humans. But there is more to account for than that. For example: - Certifications that the org has obtained - Contracts that the org has signed with customers - Compliance with laws and regulations (and international) - Insurance requirements It can add up in a hurry and can slow an org down quickly. It would be nice if an org could review all of its failures every few years and drop nearly all of its processes and procedures and start out fresh again - vowing to build around the failures of the past.
- gaius 9y ago
  It would be nice if an org could review all of its failures every few years and drop nearly all of its processes and procedures and start out fresh again - vowing to build around the failures of the past Indeed. That IT department is learning a lesson of what happens when your end users discover cloud providers and come into the office and tell their management how quick and easy it is. Managers don't know or care about the past - they only know that what should take minutes is taking months. If that department had been able to turn around a VM request in a day or two - not unreasonable - they would have been safe. Now they are being asked questions for which they have no good answers, such as, what exactly do all of you do all day?