One is caused by the other. Amazons engineers decided to split the interface in a “user hostile” manner with the stated purpose of increasing reliability… which didn’t materialise. The clunky UI did.
Or maybe you can provide a better explanation for why users had to “hunt” through hundreds(!) of product-region combinations to find that last lingering service they were getting billed $0.01 a month for?
This just doesn’t happen in GCP or Azure. You get a single pane of glass.
I mean, if you care about the reliability of your own service you would not be using the AWS UI at all. Use the api, via automation.
One of the things I find about AWS is that every service UI feels different. It's like every service was designed by a totally different team.
For all its flaws at least Azure has consistent UI.