amplify-cli: Template error: instance of Fn::GetAtt references undefined resource authcognito... when creating GraphQL API

So the issue here is that your GraphQL API is referencing the older Cognito User Pool which you’ve removed. Can you go through the amplify update api flow and update the user pool and see if the issue still exists?

SUMMARY for those might run to this issue I got the same error after running: amplify remove auth then I added new auth amplify add auth then tried to push amplify push here I got the mentioned error. As explained above the api is still referencing to the OLD cognito-user-pool ID. so here what I did: 1- amplify update api 2- For ? Select from the options below choose Update auth settings 3- For ? Choose the default authorization type for the API choose Amazon Cognito User Pool 4- For ? Configure additional auth types? choose No You will notice that the OLD cognito-user-pool ID is updated with the new one in your backEnd folder. Now you are ready to push by amplify push Problem solved

I had the same problem but running amplify update api followed by amplify push seemed to get the project back on track just fine. I agree it would be great if the API updated without user intervention but the above does work where you delete an auth resource and create a new one when using a graphql api.

Exactly. If you had done an amplify auth remove the amplify api has still an reference to the old auth one. In my opinion this is a bug

@kaustavghosh06 sure will use just amplify push. A message explaining what to do next would be useful when amplify api push detect a not valid auth stack. This thread shows that I’m not the only one confused by it.