Remix.run Logo
sofixa 3 days ago

Baring them using specific marketing terms (so you have EC2 for what are basically virtual machines), for which both the docs and the portal itself provide helpful information, what do you mean? I find GCP's console and whole set up to be slightly better, but both it and AWS are fine.

Now Azure, or anything made by VMware, you just know they hate you.

niwtsol 2 days ago | parent | next [-]

I agree that Google's console is slightly better, but a few of my gripes with AWS specifically: 1. input fields that lack basic validation so you do some action and then get an error message that is cryptic when simple "if this value selected in drop down, you can't do X". Another example of this is needing to get quota increase for your AWS account for an instance type, but nothing on the frontend tells you that, and you have to go through 3 or 4 weirdly linked support ticket/pages to figure out how to make a request for an instance. 2. As another commenter said, billing - so many pages and ways to cut the data but somehow it still seems complicated to find "which instance is attached to resource X that is costing me $Y per month" 3. Documentation not matching UI - so many PMs/TPMs over the years making resources that you find a blog/post that is a walk through, but then you find they redesigned or moved a button and that makes it difficult to follow. 4. I worked at Amazon for a bit and the internal tools feel like they were built in the early 2000s and I think I have PTSD from that which I still ascribe bad feelings towards AWS as there are similarities

I think as you use it, you start to understand the gotchas and the flows you need to do to get something working. I also appreciate there is a ton of stuff they are empowering users to do and the scale is incomprehensible, but just frustrated the UX is so poor.

I just started using Azure for another project and my goodness, I can't even login to that vs the microsoft ads account w/ the same email because of some weird MS365 permissions issue - by far the worst.

jiggawatts 3 days ago | parent | prev [-]

I love how people think Azure is somehow worse than AWS when the latter isn't even a single portal, it's many, each of which shows just one product in one region. Oh, you needed a VM with a network and some storage, including access to blobs somewhere else in the world? Just open up a dozen tabs and join the randomly generated gibberish resource identifiers yourself manually like a savage!

sofixa 2 days ago | parent | next [-]

> I love how people think Azure is somehow worse than AWS when the latter isn't even a single portal, it's many, each of which shows just one product in one region

Yep, which means that even an entire AWS region being down has no impact on anything else. Unlike Azure where a single DC in Texas being out meant no auth for anyone, anywhere in the world.

And aren't Azure and O365 infamous for having a convoluted web or multiple portals to such an extent that there are multiple websites trying to help you navigate them with direct links?

And in any case, Azure is not a serious cloud provider and anyone picking it is at best not paying attention, at worst negligent at their job (yeah I know, Azure is the cloud your bosses' boss picks after some golfing and a nice dinner). They have a ~quarterly critical, trivial to exploit, usually cross-tenant, vulnerability. Often with Microsoft having no mitigation and having the the faintest idea if it was exploited. And stalling the security researchers for weeks if not months.

The security posture of Azure is so appalling it's clear nobody at that org who has any power cares about security in the slightest. And it has been obvious for a few years now. Search Wiz's blog just for their collection of ~10 Azure CVEs. For the latest horrific one, cf: https://www.cve.org/CVERecord?id=CVE-2025-55241

doganugurlu 2 days ago | parent | prev [-]

Exactly. Just as the lord intended.

Although Azure just randomly fails, and then it turns out it actually worked but the UI had failed. But then the next step throws an obscure error message, but you get around that on a different screen, so on so forth…