AWS Amplify 构建问题 - StackUpdateComplete

Question

When running amplify push -y in the CLI, my project errors with this message:

["Index: 0 State: {\"deploy\":\"waitingForDeployment\"} Message: Resource is not in the state stackUpdateComplete"]

How do I resolve this error?

Answer 1

The "Resource is not in the state stackUpdateComplete" is the message that comes from the root CloudFormation stack associated with the Amplify App ID. The Amplify CLI is just surfacing the error message that comes from the update stack operation. This indicates that the Amplify's CloudFormation stack may have been still be in progress or stuck.

Solution 1 – “deployment-state.json”:

To fix this issue, go to the S3 bucket containing project settings and deleted the “deployment-state.json” file in root folder as this file holds the app deployment states. The bucket should end with, or contain the word “deployment”.

Solution 2 – “Requested resource not found”:

Check the status of the CloudFormation stack and see if you can notice that the stack failed because of a “Requested resource not found” error indicating that the DynamoDB table “tableID” was missing and confirm that you have deleted it (possibly accidentally). Manually create the above DynamoDB table and retry to push again.

Solution 3A - “@auth directive with 'apiKey':

If you recieve an error stating that “@auth directive with 'apiKey' provider found, but the project has no API Key authentication provider configured”. This error appears when you define a public authorisation in your GraphQL schema without specifying a provider. The public authorization specifies that everyone will be allowed to access the API, behind the scenes the API will be protected with an API Key. To be able to use the public API you must have API Key configured.

The @auth directive allows the override of the default provider for a given authorization mode. To fix the issue specify “IAM” as the provider which allows to use an "Unauthenticated Role" from Cognito Identity Pools for public access instead of an API Key.

Below is the sample code for public authorisation rule:

type Todo @model @auth(rules: [{ allow: public, provider: iam, operations: [create, read, update, delete] }]) {
  id: ID!
  name: String!
  description: String
}

After making the above changes, you can run “amplify update api” and add a IAM auth provider, the CLI generated scoped down IAM policies for the "UnAuthenticated" role automatically.

Solution 3B - Parameters: [AuthCognitoUserPoolId] must have values:

Another issue could occur here, where the default authorization type is API Key when you run the command “amplify add api” without specifying the API type. To fix this issue, follow these steps:

1. Deleted the the API
2. Recreate a new one by specifying the “Amazon Cognito user pool” as the authorization mode
3. Add IAM as an additional authorization type
4. Re-enable @auth directive in the newly created API Schema
5. Run “amplify push”

Documentation:

1. Public Authorisation
2. Troubleshoot CloudFormation stack issues in my AWS Amplify project