Kethan sai

@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...

Closing the issue due to inactivity. Do reach out to us if you require any assistance.

Hey @duckbytes, apologies on the delay in a response. Did a quick test did not observe this behavior. For technical support and deeper dive into the project on Amplify hosting,...

Closing the issue due to inactivity. Do reach out if you require any assistance with Amplify CLI.

Hey @KuzonFyre, thank you for reaching out. Could you download the `#current-cloud-backend.zip` from the S3 deployment bucket on the AWS console. The bucket name should end with deployment and contain...

@KuzonFyre could you try adding `AMPLIFY_ENABLE_DEBUG_OUTPUT` as `true` in the Amplify hosting environment variables and provide us the output?

@KuzonFyre from the logs it appears the build failed due to ``` Error: File at path: '/codebuild/output/src3871774277/src/napky/amplify/backend/auth/napkyff72303c/parameters.json' does not exist ``` from the comment https://github.com/aws-amplify/amplify-cli/issues/13667#issuecomment-2025829754 it appears you were able...

@KuzonFyre interesting, the issue does show symptoms of this. To ensure the project is in the correct state, could you zip the Amplify folder and send it to `[email protected]`?

@KuzonFyre from the information provided it appears issue doesnt appear be on the `current-cloud-backend.zip`. If are able to run `amplify push` locally and the issue is only occurring on the...

@KuzonFyre you can find the `amplify.yml` on the Amplify console under build setting