Code: 403 'RequestTimeTooSkewed' when optimizing images.
Opened this issue · 0 comments
Routhinator commented
{ [Error: API error with HTTP Code: 403]
headers:
{ 'x-amz-request-id': '72D240BCE707BA15',
'x-amz-id-2': 'W53JZ18bdyHvxWpvyutwf1MX8NxgLBcgmbafa7vjt+t8gPYSwTTHPx+lh4eegAoh',
'content-type': 'application/xml',
'transfer-encoding': 'chunked',
date: 'Wed, 23 Oct 2013 18:36:24 GMT',
connection: 'close',
server: 'AmazonS3' },
code: 403,
document:
{ Code: 'RequestTimeTooSkewed',
Message: 'The difference between the request time and the current time is too large.',
MaxAllowedSkewMilliseconds: '900000',
RequestId: '72D240BCE707BA15',
HostId: 'W53JZ18bdyHvxWpvyutwf1MX8NxgLBcgmbafa7vjt+t8gPYSwTTHPx+lh4eegAoh',
RequestTime: 'Wed, 23 Oct 2013 18:19:40 GMT',
ServerTime: '2013-10-23T18:36:26Z' } }
I get this error consistently since making changes to my setup in order to prepare for retina display. When all I was doing was resizing everything worked fine, however now that I need to double the image size and then scale the quality down, this error is plaguing my setup. The busier NodeJS is, the worse the situation gets.. eventually I hit 100% fail rate on all image uploads to S3 with this exact error.
This says to me that the request signature is being generated BEFORE imagemagick is called, so if imagemagick takes more than a few seconds, the request expires before making the attempt.. the signature should be generated afterwards, just before the request is sent to S3.