Agreed. So it sounds like Amazon is making efforts to reduce configuration failures, but users don't necessarily take the time to properly learn the tools and configure them correctly because the risk of error doesn't seem to motivate them appropriately. What can be done to change that? Naming and shaming like this?

I'm also not a devops person, so I'm definitely not debating in my wheelhouse here. It's just crazy to keep reading about a seemingly preventable problem that has the potential to do major damage in regards to data exposure.