Amplify-console: [ERROR] Amplify Stuck at Deploy Step (Updating edge config)

[khoadecormatters]

Hi. My deployment is currently stuck at the Deploy Step:
2020-11-20T04:02:17 [INFO]: Starting Deployment
2020-11-20T04:02:17 [INFO]: Updating Edge config

The weird thing is that it worked just fine earlier today.. Now its stuck on all branches at this step.

My app Id:
d90xeq8gkrh7t (us-east)

Thanks.

[yuanworks]

I am in us-east-1 and having the same issue, so I imagine it's just a hiccup or rolling update on their servers.

I will comment again here when I have any update on it.

[khoadecormatters]

Thank you @yuanworks. Thought it was just me.

[litwicki]

Hi folks, we're experiencing increased faults in us-east-1 and will update here when the issue is resolved.

[yuanworks]

Thank you for the notice @litwicki.
My build just succeeded after 32 min. 💯💯💯

[litwicki]

Closing this as it was due to an issue last night that is now resolved. If this issue happens again please reopen or create a new issue.

[JodyPSmith]

I'm having the same problem this morning (us-east 1) after a successful build it's been updating edge config for the last 17 minutes...
app Id: d31w19erw7l3sg

[ea-tal]

Same here.
30min+++ to deploy an app that used to take less than 10 min

[JodyPSmith]

2020-11-25T14:03:14 [INFO]: Starting Deployment
2020-11-25T14:03:14 [INFO]: Updating Edge config
020-11-25T14:44:04 [INFO]: Beginning deployment for application d31w19erw7l3sg, branch:beta, buildId 0000000008
ped: 92 files
2020-11-25T14:44:07 [ERROR]: Deployment terminated unsuccessfully

doesn't even complete after 30 min

[alphathesis]

I'm having the same issue as well. Been running for about 10 minutes now

[jimmy-owoa]

Same here, It's taking more than 15 minutes

[alphathesis]

Clearly something is going on at Amplify - can someone with previous experience with this issue advise whether we should let Amplify do its thing or Cancel the deploy?

[ea-tal]

should we stop using amplify for production?

[alphathesis]

My deploy is still running - anyone have any updates? My instance id is: d33emglgeqmzt1

[litwicki]

Hi folks, there is an ongoing event in us-east-1 that is causing increased error rates. We are actively monitoring and will update here when it has been resolved.

[alphathesis]

Thank you @litwicki for the update. And godspeed!

[hectorcarrillostrata]

Facing same issue here.

[carlosortizpacheco]

Facing same issue.... 40 min without success...cancelling deploy

[RoyceLeonD]

Thanks, @litwicki, just started the deployment right now. Will stay updated.

[DanielCBezerra]

I'm trying to deploy a new version for the 6 time today and still never ending... I have also some tries that are still "canceling". Experiencing these issues since this morning. My application is running in us-east-1 also. At least, I can't find any running applications that stopped to work. Just can't deploy new code to Amplify.

[litwicki]

Existings apps should not be experiencing any issues. In US-EAST-1 there are elevated error rates impacting builds and deployments that we are continuing to monitor due to an ongoing event.

[hectorcarrillostrata]

@litwicki is there an issue we could use to keep track of this ? or just keep referencing this one, even though it's closed ?

[gdickison]

I was having this same problem. The above comments say it's related to us-east-1. To get around it I just went to the upper right menu and changed servers to us-west-1. I had to go through the initial setup steps again, but I just used the defaults and it was easy peasy. Within one minute my app was deployed and good to go.

[litwicki]

@hectorcarrillostrata you can check https://status.aws.amazon.com/ for general updates

[jimmy-owoa]

Thanks @litwicki, now it's working fine

[carlosortizpacheco]

@litwicki Hi, now itś working fine

[Xantier]

@litwicki This issue is back and seems to be affecting eu-west-1 at least.

[litwicki]

@Xantier can you please open a new issue with your app details and we can have the team take a look. If you're in eu-west-1 this is unrelated to the issue from us-east-1.

[jurandircastro]

I have the same problem, my server is on us-west-2. Any news?