When the clocks of EC2 instance are skewed then the upload to S3 fails
General
Escalation
General
Escalation
Description
It's known that in EC2 instances time drift occurs. Due to that, if one has setup the backups in S3 buckets, the pbm commands start failing.
Example -
ubuntu@ip-xxx-xx-xxx-xxx:~$ pbm status
Error: get status of backups: get PITR chunks: get chunks list: get backup list: RequestTimeTooSkewed: The difference between the request time and the current time is too large.
status code: 403, request id:
A potential fix might be that we can use this parameter correctClockSkew, and set it to true
However, I don't think this option is exposed to the users yet. Since this is a backup breaking issue that sneaks up overtime, I'm marking this as high priority. Of course, you're welcome to change it if you feel otherwise.
Environment
Checked on ubuntu 20.04 EC2 instance from AWS
Smart Checklist
Activity
Show:
Aaditya Dubey December 10, 2023 at 8:12 AM
Hi ,
Closing the report, no activity for a long!
Aaditya Dubey August 1, 2022 at 9:46 AM
Hi ,
Thank you for the report. Please let me know if issue is still persists.
It's known that in EC2 instances time drift occurs. Due to that, if one has setup the backups in S3 buckets, the pbm commands start failing.
Example -
A potential fix might be that we can use this parameter correctClockSkew, and set it to true
Link - https://stackoverflow.com/questions/43641618/how-do-i-solve-the-aws-error-the-difference-between-the-request-time-and-the-c
However, I don't think this option is exposed to the users yet. Since this is a backup breaking issue that sneaks up overtime, I'm marking this as high priority. Of course, you're welcome to change it if you feel otherwise.