DynamoDB - Error Handling

DynamoDB throws an error if it fails to process a request. Each error consists of the following components: an HTTP status code, an exception name, and a message. Error management is based on your SDK that propagates errors, or on your own code.

Codes and messages

Exceptions are caught in different HTTP header status codes. 4xx and 5xx contain errors related to query and AWS issues.

Some of the exceptions in the HTTP 4xx category are listed below.

• AccessDeniedException - The client was unable to properly sign the request.

• ConditionalCheckFailedException - The condition evaluated to false.

• IncompleteSignatureException - The request included an incomplete signature.

AccessDeniedException - The client was unable to properly sign the request.

ConditionalCheckFailedException - The condition evaluated to false.

IncompleteSignatureException - The request included an incomplete signature.

The exceptions in the HTTP 5xx category are as follows:

• Internal Server Error
• Service is unavailable

Retries and backtracking algorithms

Errors come from various sources such as servers, switches, load balancers, and other elements of structures and systems. Common solutions consist of simple retries, which ensures reliability. All SDKs include this logic automatically, and you can set retry options to suit your application's needs.

For example - Java offers a maxErrorRetry value to stop retries.

Amazon recommends using a backoff solution in addition to retries to control the flow. This consists of gradually increasing waiting periods between retries and eventually stopping after a fairly short period. Note. SDKs perform automatic retries, but not exponential rollback.

The following program is an example of retry rollback −