Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jaws deploy - InvalidSignatureException: Signature expired #27

Closed
remicastaing opened this issue Aug 6, 2015 · 5 comments
Closed

jaws deploy - InvalidSignatureException: Signature expired #27

remicastaing opened this issue Aug 6, 2015 · 5 comments

Comments

@remicastaing
Copy link
Member

I've tried to deploy a lambda function and got this:

****** JAWS: Deploying your Lambda function to AWS Lambda.  This could take a few minutes...
****** JAWS: Zipping up your Lambda Function's files...
****** JAWS: Uploading your Lambda Function to AWS Lambda with these parameters: 
{ Code: { ZipFile: <Buffer 50 4b 03 04 0a 00 00 00 08 00 00 76 06 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 }
{ [InvalidSignatureException: Signature expired: 20150806T131223Z is now earlier than 20150806T131534Z (20150806T132034Z - 5 min.)]
  message: 'Signature expired: 20150806T131223Z is now earlier than 20150806T131534Z (20150806T132034Z - 5 min.)',
  code: 'InvalidSignatureException',
  time: Thu Aug 06 2015 15:20:34 GMT+0200 (CEST),
  statusCode: 403,
  retryable: true }

Any clue what happened?

@austencollins
Copy link
Member

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
Copy link

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
Copy link
Member Author

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
Copy link
Member Author

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.

@austencollins
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants