Yes, you should go talk to compliance. But for a lot less effort, you could ignore it and talk to no one.
Pulling together that meeting would only be if someone is complaining. That's what I meant by people having challenges. The goal being to head it off before it turns into a internal chat system flame-war or an HR issue that tries to single people out for blame. Hopefully people at the top will not be concerned for petty issues and are professional enough to put it to rest. It is a normal part of a companies maturing process.
I recently witnessed an argument between a dev manager and the devops team lead.
The manager manager was convinced that fixing all of the bugs would lead to perfect, 100% successful execution. The devops team lead spent an hour trying to explain why the software couldn’t achieve better reliability than AWS (the system spread across AWS zones, but each instance was contained within a single zone).
This sounds like a possible explanation for why I keep getting recommended different AWS client libraries from the boss to "solve instability" of a service that works 99.8% except for when the S3 endpoint (backblaze) has brief mystery issues.
