Our AWS error library covers high-impact exceptions across S3, IAM, EC2, Lambda, and DynamoDB with service-specific diagnostics. Each entry is written for incident workflows using RequestId and HostId evidence, policy scope checks, and quota or regional constraint analysis.
These are the highest-signal AWS pages for common production failures and the best first routes for internal linking and early user navigation.
Priority guide
Access Denied
Fix AWS AccessDenied with policy-layer diagnostics across IAM, SCP, resource policies, and trust rules to restore least-privilege access safely.
->Priority guide
Authentication Failure
Fix AWS AuthFailure: Learn the difference between authentication and authorization, validate IAM access keys, and resolve credential rotation sync iss...
->Priority guide
Throttling Exception
Fix AWS ThrottlingException with adaptive rate control, exponential backoff with jitter, and quota-aware traffic shaping for stable API behavior.
->When you need broader context, move from provider-specific pages into the matching error category or incident playbook before changing production behavior.
Showing 76-90 of 100.
AWS RequestExpired (Request Expired) means AWS received a signed request outside the allowed SigV4 time window, after a presigned URL already expired, or with a request timestamp too far in the future. In AWS APIs, this error returns HTTP 400.
AWS RequestLimitExceeded means an AWS API request-rate or account-level request quota was exceeded for the target service, operation, region, or account context.
Amazon S3 RequestTimeout means the request connection or body transfer did not progress quickly enough for S3 to continue processing it.
Amazon S3 RequestTimeTooSkewed means the caller clock is too far from S3 server time for the signed request to be accepted. This usually points to clock skew rather than queue delay or presigned URL reuse.
AWS RequestTooLargeException means the payload sent to a Lambda function exceeds the maximum allowed invocation payload size. Synchronous invocations are limited to 6MB and asynchronous invocations are limited to 256KB. The request is rejected before the function executes.
AWS ResourceConflictException is a deployment-time error that occurs when a Lambda function is already undergoing an update, deployment, or state transition. AWS serializes configuration changes, meaning a second update will be rejected if the first is still in progress.
AWS ResourceInUseException means the requested DynamoDB operation cannot be performed because the target table or index is currently being created, updated, or deleted. The resource is in a transitional state that does not accept the requested change.
AWS ResourceNotFoundException means the target resource cannot be resolved by that service in the current account, region, partition, endpoint, lifecycle state, or caller-visible scope.
AWS ServiceException means the AWS Lambda service encountered an internal error while processing the invoke request (HTTP 500).
AWS ServiceQuotaExceededException means the request exceeds a configured service quota for the account/region. Depending on service, this can surface as HTTP 400 or HTTP 402.
AWS ServiceUnavailable (Service Unavailable) means Amazon S3 is temporarily unable to handle the request. In Amazon S3, this error returns HTTP 503.
AWS SignatureDoesNotMatch (Signature Does Not Match) means AWS recalculated the SigV4 signature and it does not match the signature in the request. In Amazon S3, this error returns HTTP 403.
Amazon S3 SlowDown means S3 is applying back-pressure because request rate or request concentration is temporarily exceeding what one hot path can absorb.
AWS SubnetIPAddressLimitReachedException means Lambda could not set up VPC access because one or more configured subnets had no available IP addresses (HTTP 502).
AWS TableNotFoundException indicates that the DynamoDB operation targeted a table name that does not exist in the specific AWS Region and Account provided in the client configuration.