You should not be using AWS. Probably.
Let’s face it, choosing AWS is the cloud computing version of “nobody ever got fired for buying IBM”. There is perceived safety in choosing a popular offering — it’s what everybody else does. Many big players that product teams look up to, be it Netflix or Twitter or some other household name, have built all or some of their infrastructure on top of public cloud services. This creates scale-envy and blinds teams to the actual requirements that exist here and now.
Finally, there is the ecosystem. Having a great ecosystem is a huge benefit. It’s like an all-you-can-eat buffet. And what happens in an all-you-can-eat buffet? You tend to overeat.
AWS is increasingly under fire, due to higher than anticipated cost overruns and abandoned projects. It is surprising that there aren’t clearly defined protocols around graded access and possibly justifications for using it. Spin one and you are good to go!
Simplicity at the cost of complexity is not common sense.