AWS SDK Error - Signature not yet current

Question

I'm using the aws-sdk-php, the SesClient specifically, i've deployed an app in a customer server (hosted in DreamHost) and I'm getting this error:

Signature not yet current: 20130909T170846Z is still later than 20130909T170823Z (20130909T170323Z + 5 min.)

I'm guessing the server time is misconfigured, I'm trying to reach DH support to check on that, i bet that will take a while.

Any other ideas? The app has been deployed many times before and i've never seen this error.

If someone is looking, here is an Amazon guide for dealing with the issue https://aws.amazon.com/premiumsupport/knowledge-center/system-clock-drift-ubuntu/ — TomTom, Nov 03 '17 at 12:49

score 60 · Answer 1 · answered Dec 17 '14 at 22:25

60

I had the similar issue. I was running my CI server from an Ubuntu EC2 instance and that has the time out of sync. I synchronised the time with NTP suing

sudo ntpdate ntp.ubuntu.com

It started working fine.

answered Dec 17 '14 at 22:25

Kamrul

7,175
3
31
31

This works for Ubuntu servers on Digital Ocean as well. – tonejac Feb 27 '20 at 22:48

score 16 · Answer 2 · answered Oct 21 '19 at 05:26

16

If you are using windows, just set the current time and time zone automatically. It will resolve the issue.

answered Oct 21 '19 at 05:26

Suraj Nair

1,729
14
14

Thanks for this! Works on Mac as well (System Preferences > Date & Time > Unlock in the bottom left > Check "set date and time automatically") – Bryce Dec 27 '20 at 20:21
1

You also have to click on "Synchronize clock" (or something similar) below to make it work – matteoh Apr 05 '21 at 07:46
Thanks! I was testing something by changing my time, didn't realize it could be the root cause. – Anveeg Sinha May 17 '22 at 04:57

score 10 · Answer 3 · edited Mar 28 '17 at 07:29

I just encountered the same problem with a Django app deployed to AWS. The site error was really vague, but the error log that was emailed to me said, "JSONResponseError: JSONResponseError: 403 Forbidden {'message': 'Signature not yet current: 20150224T185106Z is still later than 20150224T185033Z (20150224T184533Z + 5 min.)'}" after a file path that pointed to Boto and Elastic Transcoder. Do the following on the server:

ntpq -p will tell you if you have ntp installed
If you don't have ntp, do sudo apt-get install ntp
sudo service ntp stop
sudo ntpdate -s us.pool.ntp.org will align your server's time with atomic clocks in the U.S. (this will need to be adjusted to your country)
sudo service ntp start

Good luck! You can read more here: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html#configure_ntp

score 10 · Answer 4 · edited Apr 13 '16 at 14:21

10

I had the same issue recently. I did the following

sudo ntpd -q -g

The -g option is needed if your clock is way out of sync. It forces ntpd to continue till it's in sync.

edited Apr 13 '16 at 14:21

Paul Roub

36,322
27
84
93

answered Apr 13 '16 at 14:13

Bish

101
1
2

rai.skumar · Answer 5 · 2015-10-01T11:52:35.610

I faced similar issue and after some investigation, found the root cause.

Reason was that, my AWS instance/server timezone and my local system timezone from where i was making RESTful call were different. AWS assumes that request is also being made from the same timezone (it just ignore gap of 5 mins, not more than that). I was able to validate this by making test call from the AWS console and checking details in the logs (giving below Java snippet)

private String getDateString() {
    Calendar cal = Calendar.getInstance();
    DateFormat dfm = new SimpleDateFormat("yyyyMMdd'T'HHmmss'Z'");
    dfm.setTimeZone(TimeZone.getTimeZone("UTC"));  //server timezone
    return dfm.format(cal.getTime());
}

score 2 · Answer 6 · answered Aug 10 '15 at 19:05

2

Just need to be sure the time of you server is 5 minutes accuracy from current time. check the AM or PM time.

answered Aug 10 '15 at 19:05

Duvan

341
2
6

score 2 · Answer 7 · answered Feb 09 '19 at 15:25

2

For windows , check your time and timezone is correct. Time of your PC must be 5 minutes accuracy from current time.

answered Feb 09 '19 at 15:25

score 0 · Answer 8 · answered Jan 11 '21 at 20:24

I have used the following for converting date to AWS request format.

String getAWSCompatibleDate() {
    var date = DateTime.now().toUtc();
    String formattedDate = DateFormat('yyyyMMddTHHmmss').format(date);
    var newDate = "$formattedDate" + "Z";
    print("Date - $date");
    print("New Date - $newDate");
    return newDate.toString();
  }

score 0 · Answer 9 · answered Feb 03 '22 at 12:54

0

On Centos6, check if the ntpd service is running.

service ntpd status service ntpd start

it worked fine, after this.

answered Feb 03 '22 at 12:54

Vikas

1
1

score 0 · Answer 10 · answered Mar 28 '23 at 08:45

0

In my case my laptop's time was not matching to my time zone when i made a sync between my laptop's time and time zone this error was gone and it started working fine

answered Mar 28 '23 at 08:45

Deepak

2,287
1
23
30

AWS SDK Error - Signature not yet current

10 Answers10

Linked