amplify push timeout: An error occured during the push operation: Your socket connection to the server was not read from or written to within the timeout period
See original GitHub issueDescribe the bug
For the past few days, as the schema started growing it has been almost impossible to reliably push any changes via amplify push --yes
The “Updating resources in the cloud. This may take a few minutes…” message only appears for one in several push attempts.
Some more logs/status updates relating to what it does at every step between compiling the schema and updating the resources in the cloud would be helpful.
I’m not sure if it’s some sort of intermittent outage related to S3 or other resources amplify push might be using. This is not an internet problem on my end.
Running amplify api push
results in a stack trace that mentions S3
as the reson for the timeout.
I have attached a screenshot below.
Error is:
Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. An error occured during the push operation: Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.
Amplify CLI Version
4.18.0
Expected behavior
Pushing should not timeout.
Screenshots
Desktop (please complete the following information):
node -v: 13.7.0 Win10 with WSL2 (Ubuntu)
Additional context
This started happening yesterday, presumably related to schema changes but I’m not sure. The processing step before it starts “Updating resources in the cloud. This may take a few minutes…” has been taking longer and longer.
Has been reported several times but the issues are closed:
https://github.com/aws-amplify/amplify-cli/issues/462 https://github.com/aws-amplify/amplify-cli/issues/501 https://github.com/aws-amplify/amplify-cli/issues/2121
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:44 (13 by maintainers)
This is a pretty big issue since you are not able to deploy any complex app that has large set of changes.
So I was able to figure out what the issue was …