AWS is pretty decent in my experience, and when managed with Terraform (which is all but a requirement if you don't want to go completely b0nkers) it's a breeze to manage.
And this is one place where I think Azure does better... I mean, the UI/UX sucks, but at least you can do everything in the UI without loosing too many brain cells. Google and AWS seem to require automation tooling to make sense, which IMO makes all of it harder to learn in practice. I tend to like learning some of those things visually first, then automate out of necessity as opposed to the other way around.
Not that I'm tethered to Azure... I've used a combination of dedicated server, DigitalOcean and Cloudflare for my personal stuff... though just started delving into the Cloudflare (edge compute) stuff.
I'm not sure I agree completely. When I was learning Terraform, trying to figure out what the options a resource had and some of the possible values, I'd make the change in the AWS UI, then re-run Terraform to see what it wanted to change back. There weren't a whole lot of things in aWS that didn't have a UI to configure somewhere.
You can also configure a resource in AWS, configure the bare minimum in Terraform (i.e. required attributes only), then run a `terraform import` and then `terraform apply`.
(Terraform does suck in that its import functionality can't spit out the HCL representation)
Yeah the AWS console UI is far from incomprehensible. Though I think what trips a lot of people up is how the resources are often something you use to compose other higher level resources.
