This has not been my experience at multiple companies with AWS, even with heavy spend – your tickets have to make it through a gatekeeper who has no more idea than you on how to fix it, and more triage than anything else.
For big flagship services you can usually get pretty good support (EC2, S3, SQS, Lambda)
For smaller/more niche services where AWS stood up a managed version of some OSS it's more hit and miss (like managed RabbitMQ).
In both cases, it definitely helps to have an open line to your TAM and send them case numbers and they'll usually do some internal nudging to keep things moving. In addition, for projects, you can usually reach out ahead of time and get some dedicated SMEs to help set things up/train you.
In either case, hopefully you've never had the displeasure of working with Azure support.
Same for the most part. Our TAMs have been great to work with and so have a number of engineers the handful of times we needed it. We've had moments of some back-and-forth at times, but overall I've been satisfied.
For big flagship services you can usually get pretty good support (EC2, S3, SQS, Lambda)
For smaller/more niche services where AWS stood up a managed version of some OSS it's more hit and miss (like managed RabbitMQ).
In both cases, it definitely helps to have an open line to your TAM and send them case numbers and they'll usually do some internal nudging to keep things moving. In addition, for projects, you can usually reach out ahead of time and get some dedicated SMEs to help set things up/train you.
In either case, hopefully you've never had the displeasure of working with Azure support.