amazon web services - How to tackle eventual consistency issues on AWS -

i'm working on project manage documents (eg: create, read, maintain different versions etc...) , plan use following aws architecture.

when document created/updated saved on version enabled s3 bucket via api gateway s3 proxy. s3 put event trigger lambda latest version , version ids , save dynamodb. once saved on dynamodb table, indexed in elasticsearch via dynamodb stream.

my plan use elasticsearch search queries. , load latest documents dynamodb. since each record has s3 version ids can query old versions s3 well.

since architecture relies on eventual consistency i.e. (s3 dynamodb , dynamodb elastic search) i'm worried not latest document data either when query elasticsearch or query dynamodb after create document.

any suggestions improvements appreciated.

thanks!

as said application architecture has multiple points eventual consistency used.

if application business case absolutely requires when query data, absolute latest version, architecture choices bad , should, example, consider using rds persistence instead.

if not, design rest of system keeping in mind getting completed put not guarantee queries return data. giving instructions on how vastly depends on application , cannot feasibly generalized.