Comment by benSaiyen
It has!
In the 2010s I always got an AWS support team to help.
Now I get handed off to an external partner of AWS certified contractors.
They are often terrible. They have no backend systems access and just run through the AWS equivalent of "reboot it", "defrag your disk". Basically trying to find an issue in my pipeline. Which they never do because it's the same TF scripts used for years.
Only once we waste time going through the motions do I get passed up to someone who can actually correct the backend issue in the AWS stack itself.
Tbf though I rarely ever have to contact AWS support at this point. The few times I have in the last 2-3 was due to issues after they rolled out an update or with a newer service we wanted to use.
Never have issues with stable services like S3, ECS, EKS, or RDS.
My last experience was with someone giving me answers that where clearly in part LLM generated: It contained payloads/configs that did not even match the actual API