A custom HTTP client on a lobby kiosk signing AWS API requests fails with SignatureDoesNotMatch after the kiosk clock drifts. What SigV4 requirement is most likely involved?
Select an answer to reveal the explanation.
Short Explanation
SigV4 is picky about the wall clock—like a parking meter that rejects a sticker from yesterday. Sync the kiosk time, and keep credentials and region straight. Turning off TLS or using the root password is not a signature fix.
Full Explanation
Signature Version 4 incorporates request timing and scoped credentials; significant clock skew commonly produces SignatureDoesNotMatch. Developers must ensure correct credentials, region/service signing scope, and reasonably accurate system time. Basic Auth with root credentials or disabling TLS does not address SigV4 validation failures.