InvalidSignatureException - client-kms

[andrespayclip]

We're running a nextJs app, using DataDog for logging on client side, we noticed some request are ending up in either a KMS error
InvalidSignatureException: Signature not yet current: 20240530T032709Z is still later than 20240530T003237Z (20240530T002737Z + 5 min.)
or
InvalidSignatureException: Signature expired: 20240530T030229Z is now earlier than 20240530T035259Z (20240530T035759Z - 5 min.)

I came accross this post, mention to set correctClockSkew to true, however the @aws-sdk/client-kms does not exposed this option

Trying to better understand how to fix this error, I'm logging currentTime and awsServerTime ->
currentTime: new Date()?.toUTCString() (browser time)
awsServerTime: headers?.date. (KMS service time)

awsServerTime
Thu, 30 May 2024 00:27:37 GMT
currentTime
Thu, 30 May 2024 03:31:09 GMT

• is this error related on the client-kms sdk?
• is an error due to an inconsistency on client side time (browser)?

We need to fix it , since it's an important error for our application and end users

tech stack
aws-sdk/client-kms: 3.213.0
nextJS typescript : 12.2.4