I would contest that claim, honestly. If you mean the Terraform AWS provider, that has very good documentation, as do all the Terraform Hashicorp providers, but

I would contest that claim, honestly. If you mean the Terraform AWS provider, that has very good documentation, as do all the Terraform Hashicorp providers, but AWS itself is all over the place. They have way too much. Run into nearly anything I can't figure out and have to go their solutions architect for and I get links to 15 different blogs that aren't even part of the main documentation. Been fighting to figure out how to authenticate a AWS VPN throug Azure AD for weeks, though to be fair there, the defect is mostly on Microsoft's side, not Amazon's. I just spent the entire day today getting rsql to finally work for querying Redshift on a M1 Mac and their documentation seems to just be flat-out wrong. All the paths they think Homebrew installs stuff into are not the right paths. They offer a arm ODBC adapter, but rsql itself only comes in x86 for some reason, so they fail if you try to use them together and you have to get the x86 ODBC instead. Also, not Amazon's fault, but I consistently get annoyed that when you web search the documentation for awscli, the top links always take you to the awscli v1, not v2. To be fair again, I don't even know that it's a solvable problem. AWS offers too many services, too many ways to access them, and makes changes too frequently. They can't just unpublish anything because someone out there is still using some combination of each version of server and client side services. But it makes it very hard to find exactly what I'm looking for. Probably made all the worse by some of the subtle differences in GovCloud, but having very little GovCloud-specific documentation.