Amplify stuck in "Provisioning" step in a monorepo.

[harrysrevis]

Before opening, please confirm:

• [X] I have checked to see if my question is addressed in the FAQ.
• [X] I have searched for duplicate or closed issues.
• [X] I have removed any sensitive information from my code snippets and submission.

Amplify Hosting feature

Deployments, Monorepo

Is your feature request related to a problem? Please describe:

I've created a monorepo using Turborepo for two React & NextJS apps. When I pushed some UI changes to the GH repo, the provisioning phase begun and stuck there for like an hour.

After waiting for some time, I cancelled and clicked "Redeploy this version" several times. This triggered an account restriction for my account and couldn't use many of the services. I opened a ticket with AWS and I'm still waiting for them to resolve it.

After checking ECS, I've seen multiple instances having been created, in every region that I manually had to delete.

What caused the issue on this?

Does anyone have any similar cases?

Thanks

Describe how you'd like this feature to work

Can anyone give me any insight?

[github-actions[bot]]

This has been identified as a feature request. If this feature is important to you, we strongly encourage you to give a 👍 reaction on the request. This helps us prioritize new features most important to you. Thank you!

[mauerbac]

Can you open a support case if you are still experiencing this?

[github-actions[bot]]

This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one.

[github-actions[bot]]

This issue has been automatically locked.