#An error occured during the operation full
#An error occured during the operation zip

Once I did that then the program was able to deploy. Once I printed the exception, it was pretty easy to figure out that the program was looking for a section in the credentials file for the project profileName. As in the first issue, an exception was getting thrown and the message was not getting written to the console.

The process I am using was working when I last worked on the project over a month ago. aws/credentials file for default profile. I was also setting environment variables for the credentials and created a. I had the useProfile option set to false and was setting credentials directly in the headless amplify init call. This did not resolve the problem, but allowed the program to move forward.ДЄfter digging deeper, I found that I was having an error due to not having the project profile name in the. gitignore so that the process could pick up my local file. At the end of the day there is a lot going on and just having error messages propagated to the log would help tremendously.ДЇirst issue was that I was getting an exception for having a corrupt local-aws-info.json file. I spent a lot of time debugging the amplify cli and was finally able to get the deploy to work. Jenkins: Dockerfile based on python:3-7-alpine imageДЄdd any other context about the problem here. You can use node -v to check the node version on your system If applicable, add screenshots to help explain your problem.Дesktop (please complete the following information): It appears to fail at const config = await configurationManager.loadConfiguration(context, aws) in the file aws.js.ДЄ clear and concise description of what you expected to happen. I have put in a lot of print statements in the amplify cli code. It would be nice to see a more informative error message to figure out what is going on. However, it did work previously and I am using the same role whether locally or via jenkins so expect it should still work. The error is likely a combination of amplify, jenkins jobs, and policies on our account.

Steps to reproduce the behavior or terminal output if applicable I tried the latest release but that causes other issues and researching the bug reports it was recommended to downgrade to 4.32.1 which is also the last version that was working for me. You can use amplify -v to check the amplify cli version on your system I have a project that needs to get to production as soon as possible, so looking for a quick workaround.

#An error occured during the operation zip

Can I manually zip the build directory and upload and then use a cli command to kick off the deployment (note that I can not upload directly in amplify console due to read only permissions in our production environment). Please let me know if there is an alternative that I can follow given that the build directory is being created. While ideally I would like to get this fixed.

#An error occured during the operation full

I was on with support for over 3 hours today and a full recording was made of the process I am following. If I kick off the job again, it will normally not throw that error and continue with the rest of the process. I also see a random error 'An error occurred during the push operation: The AWS Access Key Id you provided does not exist in our records.' This error stops well before the above mentioned problem. When run via Jenkins, the same role is used that is used when I run locally. This process was working about a month ago. In my production environment I do not have console access so need to deploy everything via Jenkins. I am working in a dev environment where I do have console access. The last line before the error is 'Find out more about deployment here: bit.ly/CRA-deploy.' It appears to have completed cloudformation updates and built the deployment package. Using headless amplify publish, I am getting 'An error occurred during the publish operation'. Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the