jaws deploy - InvalidSignatureException: Signature expired about serverless

[ac360]

Hmm, I'm not sure. Try the AWS developer forums in the interim: https://forums.aws.amazon.com/forum.jspa?forumID=186&start=0

And when I get home tonight, I'll look into this.

[olivierkaisin]

Usually this happens when your machine's clock get out of sync. Depending of your OS there are different ways to force resync it.

For example on Ubuntu: sudo ntpdate ntp.ubuntu.com

I hope this helps.

[remicastaing]

Is this time to deploy normal (32 min)?

[2015-08-07T10:36:21.988Z] ****** JAWS: Deploying your Lambda function to AWS Lambda.  This could take a few minutes...
[2015-08-07T10:36:34.351Z] ****** JAWS: Zipping up your Lambda Function's files...
[2015-08-07T10:36:35.116Z] ****** JAWS: Uploading your Lambda Function to AWS Lambda with these parameters: 
[2015-08-07T10:36:35.117Z] { Code: { ZipFile: <Buffer 50 4b 03 04 0a 00 00 00 08 00 8b 64 07 47 4c 26 27 f8 d9 00 00 00 fa 00 00 00 0a 00 00 00 65 76 65 6e 74 2e 6a 73 6f 6e 25 8e 4d 8f 82 30 14 45 f7 fe ... > },
  FunctionName: 'api_users_show',
  Handler: 'index.handler',
  Role: 'arn:aws:iam::343927519172:role/jaws_lambda_role',
  Runtime: 'nodejs',
  Description: 'None',
  MemorySize: 513,
  Timeout: 5 }
[2015-08-07T11:08:48.274Z] { [InvalidSignatureException: Signature expired: 20150807T110048Z is now earlier than 20150807T110348Z (20150807T110848Z - 5 min.)]
  message: 'Signature expired: 20150807T110048Z is now earlier than 20150807T110348Z (20150807T110848Z - 5 min.)',
  code: 'InvalidSignatureException',
  time: Fri Aug 07 2015 13:08:48 GMT+0200 (CEST),
  statusCode: 403,
  retryable: true }

[remicastaing]

I just started over to deploy a lambda function with the latest version of jaws: it works and within no time (32s).
Thanks, @ac360, @olivierkaisin.

[ac360]

@remicastaing Sorry, I lost track of this issue. Please re-open this Issue if it troubles you again!