cloud

AWS Errors

AWS spans 200+ services, each with its own error catalogue. Common failures: IAM permissions (AccessDeniedException), S3 (NoSuchBucket, 403), Lambda (timeout, throttling), DynamoDB (ProvisionedThroughputExceededException).

AWS error codes follow a service-prefixed pattern: `S3.NoSuchBucket`, `IAM.AccessDenied`, `Lambda.TooManyRequestsException`. Most production issues stem from IAM policy gaps, region mismatches, or service quotas. Use CloudTrail to trace the exact API call that failed and the principal that made it.

Permissions (1)

AccessDeniedException 403

IAM Permission Denied

The IAM principal (user, role, or assumed role) making the request does not have an `Allow` statement for the action and resource being called, or an explicit `Deny` somewhere in the evaluation chain blocks it.

Not found (1)

NoSuchBucket 404

S3 Bucket Does Not Exist

The S3 bucket name in your request does not exist in the region your client is calling. Either the name is misspelled, the bucket was deleted, or your client is pointed at the wrong region for a bucket that exists elsewhere.

Rate limits (1)

ThrottlingException 400

API Rate Limit Exceeded

You exceeded the per-second or per-account API request limit for an AWS service. Most AWS APIs use a token bucket — sustained or bursty traffic above the bucket refill rate gets throttled.

Official docs

https://docs.aws.amazon.com/general/latest/gr/api-retries.html

Status page

https://health.aws.amazon.com/health/status

Support

https://aws.amazon.com/support/

Related services

Google Cloud

Cloud platform