search

aws-amplify / amplify-hosting

AWS Amplify Hosting provides a Git-based workflow for deploying and hosting fullstack serverless web applications.
https://aws.amazon.com/amplify/hosting/
Apache License 2.0
456 stars 115 forks source link

[ERROR] Amplify Stuck at Deploy Step (Updating edge config) #1250

Closed khoadecormatters closed 1 year ago

khoadecormatters commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

Thank you @yuanworks. Thought it was just me.

litwicki commented 3 years ago

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

yuanworks commented 3 years ago

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

litwicki commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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

JodyPSmith commented 3 years ago

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

ashishbpatel commented 3 years ago

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

jimmy-owoa commented 3 years ago

Same here, It's taking more than 15 minutes

ashishbpatel commented 3 years ago

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 commented 3 years ago

should we stop using amplify for production?

ashishbpatel commented 3 years ago

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

litwicki commented 3 years ago

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.

ashishbpatel commented 3 years ago

Thank you @litwicki for the update. And godspeed!

hectorcarrillostrata commented 3 years ago

Facing same issue here.

carlosortizpacheco commented 3 years ago

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

RoyceLeonD commented 3 years ago

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

DanielCBezerra commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

@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 commented 3 years ago

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 commented 3 years ago

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

jimmy-owoa commented 3 years ago

Thanks @litwicki, now it's working fine

carlosortizpacheco commented 3 years ago

@litwicki Hi, now itÅ› working fine

Xantier commented 3 years ago

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

litwicki commented 3 years ago

@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 commented 3 years ago

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

pcossioa commented 3 years ago

Please reopen the issue, I'm facing it again.

iceye commented 2 years ago

+1 today eu-central-1 at 16:03-16:15 GMT

NotSoShaby commented 2 years ago

Happens now as well us-east-1

p3v9d5ui commented 2 years ago

Happening for now with eu-central-1. "Updating Edge config" been stuck for almost 4 hours.

Athena96 commented 2 years ago

hi @p3v9d5ui can you share your appId

ghost commented 2 years ago

@iceye @NotSoShaby @p3v9d5ui we are currently working on mitigating this. In the mean time, can you try re-deploying your apps? Also try to minimize the number of concurrent builds you have running, if this applies to your use case.

p3v9d5ui commented 2 years ago

@Athena96 , my app id is ddgrnop6ksu96.

I'm experiencing multiple serious issues with Amplify now. There's this issue, but even when a deploy does succeed, as happened just now, an old version is still being served.

And, frustratingly, if the deploy succeeds, and the resulting app version is correct, it will then revert to an old version after some time -- usually within 30 minutes.

Can someone from the Amplify team please give an update on what is happening with the service? This is a serious issue, which is impacting our production service and all of our customers.

Athena96 commented 2 years ago

Thanks @p3v9d5ui is this behavior happening on every new build (where after 30m it reverts to an old version)? If not, can you share the jobs it this behavior is happening? i.e. new job Id and job it reverts back to.

p3v9d5ui commented 2 years ago

Hi @Athena96 , I'm not sure how to get this information. Are you referring to the build number?

Also, note that AWS support is also working on this issue.

dramirez-cs commented 2 years ago

Got an error for increased API error rates and latency for us-east-1 and then my amplify upgrade is acting up at the "Deploy" stage. This sounds like the same issue as in 2020 when this question first started.

garysm commented 1 year ago

I am receiving this error as well in us-east-1. App ID: d1za7h7154qxbl

UPDATE: One of my builds finished but other is still stuck. UPDATE: Both finished and took approximately 30 minutes to finish. All other builds have not taken nearly as long.

faze11 commented 1 year ago

I am also receiving this error currently in us-east-1

app ID: d1r75ic8bc1hlk

jbarnickol commented 1 year ago

Same issue here for app ARN: arn:aws:amplify:us-east-1:250853967324:apps/d17s4o0gti878f

ghost commented 1 year ago

@jbarnickol @faze11 @KamranBromand @garysm thanks for reporting this issue. We are currently investigating this behavior and will update with next steps shortly.

jbarnickol commented 1 year ago

@hloriana Thanks for the quick response! Mine just went through on its own a couple minutes ago without me taking further action.

ghost commented 1 year ago

This issue is resolved for folks who experienced a failed deployments. If you experience further deployment failures, please open a new issue with the bug report template. Thank you!