Amazon Web Services Question posted in
The official Amazon Web Services documentation can be found here.

Amazon web services – AWS Amplify deployment permanent "pending" state

Amplify job is in pending state

So GitHub repository and Amplify are connected. When I push anything to the active branches it triggers Amplify (webhook is working correctly), and creates a new deployment, but the build is not started. There are no logs or messages which can point to the problem. I’ve discovered only one similar problem in Discord, with only one proposition to check Cloudformation for any rollbacks that may prevent the deployment. I’ve not found such.

Application framework: React.
Backend is not hosted on Amplify.

I’ve tried to find similar problems and their solutions. I have been looking through Amplify issues, the Discord channel, checking AWS settings and environment variables, searching for any logs, stopping and starting jobs using AWS CLI, and checking permissions.

Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    The solution to the problem is straightforward. There was a problem with the payment and, as an IAM user, I hadn't permission to check this, while stakeholders told me everything was OK. :)


  2. 0

    The following steps can be done to troubleshoot the issue of AWS Amplify deployment getting stuck in a permanent "pending" state:

    • Check that the settings of your builds are correctly configured within the Amplify console. Amplify.yml should be configured correctly.
    • Check that you are deploying the correct branch and configured in the Amplify console.
    • Check if any failed CloudFormation stacks prevent your deployment from completing.
    • Check that no rollbacks or updates are in progress, or if one has failed.
    • Be sure that IAM roles utilized by Amplify have enough permissions.
    • Check that the Amplify service role has permission to access resources as required—for example, the S3 and CloudFront buckets.
    • Check the Amplify console for any logs that may give some clue about the error.
    • Sometimes, it gets resolved by canceling this stuck deployment and creating a new one.
    • Be certain that none of AWS’s service quotas have been exceeded, which may be causing issues with your deployment.
    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search