Aws-cli: Connection was closed before we received a valid response from endpoint URL

[bdrgn]

I am receiving the above error when trying to upload my code to Lambda using the cli:

aws lambda update-function-code --function-name AvitoFlats --zip-file fileb://function.zip

One day ago it worked fine like many times before.

Tried:

• Different networks
• Restarting my machine
• Updating AWS CLI to the latest version

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

[KaibaLopez]

Hi @bdrgn ,
could you add --debug to the command and show me what you get? (Remember to sanitize personal info).

[bdrgn]

First this and then some huge nonsensical mess which freezes my machine.
I will try to make sense of this next if current output is not informative.

[bdrgn]

Looks like this.

[KaibaLopez]

Hmmm,
yea not really much I can see from the logs, it does sound like it's a connection problem, is the zip file very heavy or is your connection unstable? Could you be trying to connect through a different region?
sorry that I can't be of much help, kind of shooting at the dark here since I don't have much information to go by... I can't reproduce either.

[dvillevald]

I am having the same problem trying upload zip folder to lambda

[PranavMonotype]

Its can be a network error.
If you are connected to a VPN , try after disconnecting it
try with better internet connection
my case, closing the VPN worked

[github-actions[bot]]

Greetings! It looks like this issue hasn’t been active in longer than a week. We encourage you to check if this is still an issue in the latest release. Because it has been longer than a week since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or add an upvote to prevent automatic closure, or if the issue is already closed, please feel free to open a new one.

[nestradarand]

damn, I'm having this same exact problem as well

[miesismore]

Same problem here, uploading a 12GB .7z compressed file, is there any problem with this size? is better to upload uncompressed or at lower sizes? (i read CLI was recommended for >160Gb so i guess is no problem with this).
Using AWS CLI 2.0.19, 64 bit, Win 10

[itsdarrylnorris]

I am getting the same error sometimes. Any workarounds?

[szanata]

I was having the same issue. One day it worked, the very next day, not.
In my case I was uploading a lambda layer with a ~20M zip file. My script was using AWS 2.0 inside a docker container.
What I did to solve the issue was to restart the Docker client and reconnect the WIFI. So I guess this is indeed related to a network error.

[itsdarrylnorris]

If you are on a VPN or slow connection this will happen all the time. My recommendation is to switch to a faster internet connection and get off any VPN if possible.