Lambda upload timeouts

Question

I usually upload my lambda like this:
```
aws lambda update-function-code \
	--function-name TulipApiTestV1 \
	--zip-file fileb://out/aws-tulip-test-linux-amd64.zip \
	--no-paginate
```

but it has been super slow.  Just now I got this:

> Connection was closed before we received a valid response from endpoint URL: "https://lambda.us-east-1.amazonaws.com/2015-03-31/functions/TulipApiTestV1/code".

I decided to try it from the console and got something even worse:

> Signature expired: 20220525T144001Z is now earlier than 20220525T144103Z (20220525T144603Z - 5 min.)

(I'm in development, there's no signature at all).

I tried it again a few times, then stepped away for a while and came back and now it's working, but it's absurdly slow.

Is this just a glitch?

Answer

I am not sure why it happened to you and now it works. Could it be that the zip file is large? If the file is larger than 50MB it must be uploaded to S3 first and then update the function code from there. I would recommend using SAM to deploy. It will package the code and upload it to S3 on your behalf.

Answer

Nope my ZIP file is really small, it's about 7 megabytes.

Answer

I'm seeing more or less the same thing.  I'm using the web console, trying to upload a 3.6MB .zip, and the UI times out repeatedly.  This is an existing project and I've done this successfully many times before with a slightly smaller .zip (3MB - 3.2MB), but it's been 11 days since my last upload.

CLI:  
`% aws lambda update-function-code --function-name  --zip-file fileb://<.zip path>`

`Connection was closed before we received a valid response from endpoint URL: "https://lambda.us-east-2.amazonaws.com/2015-03-31/functions//code".`

Is there an outage going on?

us-east-2  
macOS Monterey 12.2.1  
Chrome Version 110.0.5481.100 (Official Build) (x86_64)  
Tested upload speed 4.7mbps

Answer

Yes, it was an outage.  Web console and CLI both work now.

Lambda upload timeouts

関連するコンテンツ