Converting from Expired API Key to Cognito causes Cloudformation to fail.

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the official AWS Amplify Console forum

Describe the bug Switching to Cognito auth type from an expired API key causes amplify push to fail with the error 404 not found.

To Reproduce Steps to reproduce the behavior:

1. Create a new project and use API Key as the auth type
2. Expire the API key
3. Convert existing project to Cognito using amplify api update
4. Execute amplify push
5. This would cause Cloudformation to fail.

Expected behavior Auth type to switch to Cognito instead of API key

Screenshots

Additional context Using Amplify for Javascript with React. Using Amplify version 1.1.6

[ChristopheBougere]

To be more specific you don’t edit the value but you redeploy the stack with a new value for the parameter.

• In the console, you probably have 2 failing stacks. One is the root, the other one is the API (a nested stack)
• Select the nested stack, and click on update
• Confirm that you want to update the nested stack
• “Use current template”
• Then you can update parameters (APIKeyExpirationEpoch)
• Confirm and deploy This kind of manual action is usually not recommended because you could desynchronize with your amplify project. But it worked for me and other solutions didn’t work.

[gitzhouxinyu1]

Any updates? I still got the same error with latest cli