[deboyd]

@digiltd

I am back again with (slightly) more skill. I have progressed through all my issues and now, have landed upon this "time" issue like many other people on this thread. If it is true that my PC time is out of sync with the destination clock, then changing my PC time to equal the destination clock should fix the problem.

My PC clock is currently in Central Time and the destination clock is US-West-2. I changed my PC clock to be Pacific Time and re-ran the command to upload .env to AWS. It took the same 10 minutes and had the exact same error. Am I using the right time zone for US-West-2? Any other thoughts?

Here is my specific error read out:


botocore.exceptions.ClientError: An error occurred (InvalidSignatureException) when calling the CreateFunction operation: Signature expired: 20170325T155703Z is now earlier than 20170325T160002Z (20170325T160502Z - 5 min.)

Thank you in advance!

I have this issue as well. Synced my time and tried to deploy on Mac and Linux machines with no progress.

Please, if you make some progress let us know and I will do the same.

I'm not sure if this is relevant, but the last file location accessed during the upload to Lambda is File "c:\python27\lib\site-packages\botocore\client.py", line 543, in _make_api_call
raise error_class(parsed_response, operation_name)

If I open this file, there is a paragraph which directly talks about time.

"This class handles taking out the relevant arguments from the endpoint
resolver and determining which values to use, taking into account any
client configuration options and scope configuration options.

This class also handles determining what, if any, region to use if no
explicit region setting is provided. For example, Amazon S3 client will
utilize "us-east-1" by default if no region can be resolved.s"

Just throwing it out there incase it helps us come closer to a solution.

Thanks!
Dan