DynamoDB supports eventually consistent and strongly consistent reads.

Eventually Consistent Reads

When you read data from a DynamoDB table, the response might not reflect the results of a recently completed write operation. The response might include some stale data. If you repeat your read request after a short time, the response should return the latest data.

Strongly Consistent Reads

When you request a strongly consistent read, DynamoDB returns a response with the most up-to-date data, reflecting the updates from all prior write operations that were successful. However, this consistency comes with some disadvantages:

Strongly consistent reads are not supported on global secondary indexes.

Strongly consistent reads use more throughput capacity than eventually consistent reads. If there is a network delay or outage, a strongly consistent read might not be available and DynamoDB may return a server error (HTTP 500). For details, see Read/write capacity mode

If read requests do not reach the Leader node on the first attempt, then strongly consistent reads may experience a higher latency.