That’s massively disappointing. I’ve contributed fixes to documentation over a dozen times in the last couple of years.
They should fix their process instead of removing the ability to contribute fixes to docs.
They should fix their process instead of removing the ability to contribute fixes to docs.
Honestly don't know if this is true or not.
The only real complaint majority of people have with aws is price and 95% of the time it’s because they can’t spend 10 minutes doing so math or building their setup right to not cost them.
Curious to hear your specific complaints with GCP.
My biggest complaint on GCP is the support. With AWS when needing support we get responses in 10m to a few hours depending on the severity of the issue. I raised a ticket with GCP about 3 months ago due to a VM vanishing. Could connect to it but not see it in their UI. Took a week to get it back with no explanation. Just magically appeared and ticket closed. Granted our bill with AWS is 25k/m while GCP is about 2k. Thankfully we don’t run production on GCP. Just use it for testing (as we do with Azure)
It sounds like you might be using the free community support that comes with any amount of GCP usage, is that right? Just like AWS, you get community support for free and they offer paid support tiers for a monthly fee with minimum response time for each severity level. If you are paying, the highest response time appears to be one business day. If you are paying for support and didn't get it, that does sound like a serious problem.
Aws service integration would be another thing they do better. The level of service integration is kinda insane.