Why are there a high number of UserErrors on my DynamoDB table?

Last updated: 2020-07-01

Why are there user errors on my Amazon DynamoDB table?

Short description

The Amazon CloudWatch UserErrors metric aggregates client-side errors (HTTP 400 status) for all tables and streams in the same Region and account. The presence of user errors doesn't necessarily mean that the current table has a 400 error.

Exceptions such as IncompleteSignatureException, ResourceNotFoundException, and ValidationException result in user errors. The UserErrors metric doesn't capture ProvisionedThroughputExceededException or ConditionalCheckFailedException. For more information, see DynamoDB metrics.


Here are the applicable statistics for UserErrors:

  • Sum: the total number of user errors during the time frame
  • SampleCount: the total number of requests that resulted in user errors during the time frame

Resolve user errors on the client side:

  1. To find the root causes of user errors, note the time frame that's specified in the UserError metric. Then, check that time frame in the client's application logs.
  2. To prevent user errors, add try-catch or if-then statements to catch and respond to exceptions. For more information, see Error handling with DynamoDB.

Did this article help you?

Anything we could improve?

Need more help?