AWS Amplify Deployments Stuck in Provisioning Phase

Question

Issue Summary: AWS Amplify Hosting deployments consistently get stuck in the "Provisioning" phase for 5-9 minutes before timing out, preventing any builds from completing.

Environment:

Service: AWS Amplify Hosting
Region: US East 1 (N. Virginia)
Platform: Next.js SSR application
Compute: Standard 8GB
Problem Details: Deployments remain indefinitely stuck in the provisioning phase of the BUILD step without progressing to actual build execution. No build logs are generated during this time, indicating the build environment is never successfully allocated.

Current Live Example: A deployment started at 17:59 UTC today has been stuck in provisioning for over 10 minutes with no progression.

Pattern Observed:

Issue affects multiple consecutive deployment attempts
Occurs with both new commits and previously successful commits
Problem persists across different commits and timeframes
No build or install steps ever begin
Troubleshooting Steps Attempted:

Reconnected GitHub repository integration
Cancelled and retried deployments multiple times
Tested with previously known-working commit versions
Verified GitHub App permissions and webhook connectivity
Confirmed no recent changes to build configuration or environment variables
Expected Behavior: Deployment should progress from provisioning to source download and build within 1-2 minutes.

Actual Behavior: Deployments remain stuck in provisioning phase for extended periods (5-9 minutes) before being cancelled or timing out.

Impact: Production deployments are completely blocked, preventing any code updates from being deployed.

Request: Please investigate potential regional infrastructure issues or service degradation affecting Amplify build provisioning in US East 1.

re:Post Agent · Answer

I understand you're experiencing significant deployment issues with AWS Amplify Hosting where your Next.js SSR application deployments are getting stuck in the provisioning phase. This is clearly blocking your production deployments, which is a critical situation.

Based on the information provided, this appears to be an operational issue rather than a configuration problem, especially given that:
- Previously successful commits are now failing
- Multiple consecutive attempts show the same behavior
- You've already performed standard troubleshooting steps
- No build logs are being generated, indicating the build environment isn't being allocated

For immediate assistance with this service disruption, I recommend:

1. **Check the AWS Service Health Dashboard** for any reported issues with AWS Amplify in US East 1
2. **Open an AWS Support case** immediately, as this appears to be a service-level issue that requires investigation by the Amplify team
3. **Consider temporarily deploying to a different region** if your architecture allows, to unblock your production deployments

When opening your support case, include:
- Your Amplify App ID
- Specific deployment IDs that are stuck
- The exact timestamps of failed deployments
- Screenshots of the provisioning phase timeout
- All the troubleshooting steps you've already completed

Since Amplify is built on AWS serverless technologies including AWS Lambda, Amazon S3, and Amazon DynamoDB, the provisioning issue could be related to resource allocation in the underlying infrastructure. However, this level of investigation requires direct access to your account and service logs, which only AWS Support can provide.

If you have an Enterprise or Business support plan, I'd recommend using your Technical Account Manager (TAM) or opening a high-severity case to expedite the investigation.  
**Sources**  
[AWS Amplify | Extensible Web & Mobile Apps | Amazon Web Services](https://aws.amazon.com/amplify/extensibility/)

AWS Amplify Deployments Stuck in Provisioning Phase

Add your answer

Relevant content