This article covers two different errors that occur when performing different tasks, but have the same root cause:
When adding S3 Object Storage to Veeam Console, Veeam displays the follow error:
Failed to list S3 buckets: check if the specified account has required permissions REST API Error: 'S3 Error: The difference between the request time and the current time is too large. Code: RequestTimeTooSkewed'
Job fails during Offload after the backup job runs, with error:
Invalid credentials for Amazon S3 endpoint. See logs for details.
Click to Expand and view log file examples
In the Task Logs, it will be as below:
Error Amazon REST error: 'S3 error: The difference between the request time and the current time is too large.. Code: RequestTimeTooSkewed', error code: 403. Other: RequestTime: '20210721T040936Z', ServerTime: '2021-07-17T10:12:34Z', MaxAllowedSkewMilliseconds: '900000'
If the error occurs during SOBR Offload, it will be visible in ArchiveCleanup.Gate Log as below:
aws | WARN|HTTP request failed, retry in  seconds, attempt number , total retry timeout left:  seconds aws | >> |REST API error: 'S3 error: The difference between the request time and the current time is too large. aws | >> |Code: RequestTimeTooSkewed', error code: 403 aws | >> |tr:Request ID: aws | >> |Other: RequestTime: '20210720T101336Z', ServerTime: '2021-07-17T10:13:41Z', MaxAllowedSkewMilliseconds: '900000'
The failure occurs because AWS allows for a maximum of 15 minutes of time stamp variation between the server and Gateway Server (Client).