AxiosError: read ECONNRESET about amplify-cli

[ykethan]

Hey @Sanoodia, thank you for reaching. Is this occurring on a amplify mock function?
If this is on the Lambda invocation on the console, implementing a error handling and retry logic may help in mitigating this behavior, refer to the Lambda documentation providing additional information. If this does not mitigate the issue, I would suggest reaching out to AWS technical support for Lambda for a deeper investigation.

[Sanoodia]

here are the logs of my axio request
Error: read ECONNRESET
at AxiosError.from (/opt/nodejs/node_modules/axios/dist/node/axios.cjs:836:14)
at RedirectableRequest.handleRequestError (/opt/nodejs/node_modules/axios/dist/node/axios.cjs:3086:25)
at RedirectableRequest.emit (node:events:517:28)
at RedirectableRequest.emit (node:domain:489:12)
at eventHandlers. (/opt/nodejs/node_modules/follow-redirects/index.js:38:24)
at ClientRequest.emit (node:events:517:28)
at ClientRequest.emit (node:domain:489:12)
at TLSSocket.socketErrorListener (node:_http_client:501:9)
at TLSSocket.emit (node:events:517:28)
at TLSSocket.emit (node:domain:489:12)
at Axios.request (/opt/nodejs/node_modules/axios/dist/node/axios.cjs:3876:41)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async getPaginatedData (/opt/envHelpers.js:84:22)
at async Object.getLoadById (/var/task/sync_sdk.js:162:16)
at async exports.handler (/var/task/index.js:464:30)

[ykethan]

@Sanoodia thank you for providing the log, the error read ECONNRESET indicated an network/connection to a server was reset while the request was being made on the AWS Lambda. The AWS technical support for Lambda should be able to assist you in diving deeper on the service side.