amplify-cli: Backend deployments Throttling: Rate exceeded
This issue has happened before and also solved before like in aws-amplify/amplify-console#88
So again the same story, all resources could be pushed via amplify push on my local system without a single issue, but build pipeline fails to build it with the error below:
# Starting phase: build
# Executing command: amplifyPush --simple
2019-12-17T17:22:04.214Z [INFO]:
2019-12-17T17:22:04.216Z [INFO]: For more information on AWS Profiles, see:
https://docs.aws.amazon.com/cli/latest/userguide/cli-multiple-profiles.html
2019-12-17T17:22:04.619Z [INFO]: Amplify AppID found: d1haz5673z20fp. Amplify App name is: fcf-personalization}
2019-12-17T17:22:04.752Z [INFO]: Backend environment dev found in Amplify Console app: fcf-personalization
2019-12-17T17:22:47.891Z [INFO]:
2019-12-17T17:22:48.398Z [INFO]: Note: It is recommended to run this command from the root of your app directory
2019-12-17T17:22:50.369Z [WARNING]: - Initializing your environment: dev
2019-12-17T17:23:30.227Z [WARNING]: ✔ Initialized provider successfully.
2019-12-17T17:23:33.649Z [WARNING]: - Updating resources in the cloud. This may take a few minutes…
2019-12-17T17:23:34.068Z [INFO]: Throttling: Rate exceeded
at Request.extractError (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/protocol/query.js:50:29)
at Request.callListeners (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:683:14)
at Request.transition (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request.<anonymous> (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:38:9)
at Request.<anonymous> (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:685:12)
at Request.callListeners (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
2019-12-17T17:23:34.070Z [WARNING]: ✖ An error occurred when pushing the resources to the cloud
2019-12-17T17:23:34.071Z [WARNING]: ✖ There was an error initializing your environment.
2019-12-17T17:23:34.071Z [INFO]: init failed
2019-12-17T17:23:34.073Z [INFO]: Error: Project stack doesn’t exist
at Response.cfnModel.describeStacks.err (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-provider-awscloudformation/src/aws-utils/aws-cfn.js:232:22)
at Request.<anonymous> (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:364:18)
at Request.callListeners (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:683:14)
at Request.transition (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request.<anonymous> (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:38:9)
at Request.<anonymous> (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:685:12)
2019-12-17T17:23:34.215Z [ERROR]: !!! Build failed
2019-12-17T17:23:34.215Z [ERROR]: !!! Non-Zero Exit Code detected
2019-12-17T17:23:34.215Z [INFO]: # Starting environment caching…
2019-12-17T17:23:34.216Z [INFO]: # Environment caching completed
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 15 (3 by maintainers)
Commits related to this issue
- fix(amplify-provider-awscloudformation): add retry logic When a stack gets updates, cloudformation provider checks the existance of root stack by running a describe stack API call. On Amplify console... — committed to yuth/amplify-cli by yuth 5 years ago
- fix(amplify-provider-awscloudformation): add retry logic (#3020) When a stack gets updates, cloudformation provider checks the existance of root stack by running a describe stack API call. On Amplif... — committed to aws-amplify/amplify-cli by yuth 5 years ago
Also have hit this error again on my project, using Amplify CLI 4.6.0, currently blocked from deploying