Compare AWS ThrottlingException and GCP RESOURCE_EXHAUSTED to separate rate limiting from quota/resource exhaustion and choose the remediation path.
Last reviewed: February 20, 2026|Editorial standard: source-backed comparison guidance
HTTP/1.1 400 Bad Request
Content-Type: application/x-amz-json-1.0
x-amzn-RequestId: 12345678-aaaa-bbbb-cccc-1234567890ab
{
"__type": "ThrottlingException",
"message": "Rate exceeded"
}HTTP/1.1 429 Too Many Requests
Content-Type: application/json
{
"error": {
"code": 429,
"status": "RESOURCE_EXHAUSTED",
"message": "Quota exceeded for this operation."
}
}No. They are related saturation signals but not identical. AWS ThrottlingException is primarily a throttling/admission-control signal, while GCP RESOURCE_EXHAUSTED covers quota and broader exhausted-resource cases.
Not always. Use bounded retries with jitter first; if failures persist and quota telemetry shows sustained exhaustion, move to quota/capacity remediation.
No. 429 is common for REST quota excess, but service/protocol mappings vary. Use provider status/reason and quota telemetry for final classification.
Compare AWS AccessDenied and GCP PERMISSION_DENIED to isolate authorization deny layers, separate auth failures, and apply precise IAM fixes fast.
Fix 401 Unauthorized vs 403 Forbidden by separating authentication failures from authorization denials, then apply the right login or permission fix fast.