Problem deploying kodi skill to AWS

[sphirst]

I've followed all the steps detailed in this read me; https://github.com/m0ngr31/kodi-alexa#aws-lambda. I'm having some issues deploying to AWS - it hangs for quite some time while deploying then comes up with the following message.
Can you suggest where I am going wrong?

[jimjkelly]

Is your clock right? AWS can be pretty sensitive to clock drift. That'd be the first thing I'd check based on the error message.

[sphirst]

First thing I checked - time is set automatically and I've checked it against https://time.is/ and it looks correct

[jimjkelly]

Hmm, out of curiosity could you run pip list and paste the output in here?

[sphirst]

[jimjkelly]

Versions all seem good. Back to timestamps - it seems looking at the timestamps being printed the machine thinks it's January 12th, if I'm reading that correctly? 20170112T213212Z. Can you confirm for sure that your computer's clock isn't set to that date?

[jimjkelly]

And just to confirm this isn't a VM or anything, right?

[sphirst]

Not sure why that might be the case - it's definitely 16/1 and VM is virtual machine right? I'm operating Windows 10, no other OS emulation.

[jimjkelly]

One stab in the dark idea - how long did the program take to run take before you got that error?

[sphirst]

It hung on "Adding new kodi-alexa-master lambda" for 2-4 minutes.

[jimjkelly]

Hmm. This is definitely pretty strange. I'll keep digging a bit and see what I can turn up, but in the meantime the two things I might suggest:

Lame I know, but this definitely is something to do with the clock, maybe it'll get unstuck with a restart?

The other thing might be to run it, take note of the timestamp printed in the error, and try and adjust your local clock to match it.

You shouldn't need to do either of these things though, given that you are using NTP and presumably have your timezone set correctly. But yeah I'll continue to poke at it, not sure when/if I'll come up with an answer though, since it seems to be something on your system and how it plays with the AWS servers and timestamps.

[sphirst]

I'll try and fiddle around with it. Do you think there could be any problems with the .env file I'm trying to upload or any region settings with AWS?

[jimjkelly]

I wouldn't think so. I deploy to us-west-2 and live in Germany, so I'd imagine I would have hit issues with that if it would be a problem. This error does tend to pretty reliably be an issue with the clock being off from Amazon's, and I do find it really odd that the timestamp it's printing out is several days off, but yeah obviously your clock seems right (I assume you are GMT, based on the photos?).

I think I have a Windows 10 VM, I may try and reproduce your stack and see if I can reproduce the problem, but I suspect it's a weird local clock thing.

[sphirst]

Regarding the earlier date, I've just realised that that was actually a screenshot from when I tried it on 12th Jan - thus it was timestamped with that day!
Having tried it again today, the timestamp is 20170117 so it's accurately displaying the right date according to my clock settings
You're right, I am GMT