This morning, seems like AWS was fixed. But, I am now getting this error: NoSuchDistribution: The specified distribution does not exist.
This makes sense since I deleted the multiple new CloudFront instances created on each Amplify deploy. Is there a way to tell Amplify (within the web console) to use previous/old CloudFront distribution ID?
I'm having the same exact problem but more recently. We hadn't make any update for a while. Did you ever figure out why?
Was Cloudfront affected by the Friday 9th September outage in the US-EAST-1 Region?asked 25 days ago
Why does deploying AWS Amplify create a new CloudFront distribution every time. Bug? (since September 9th)asked a month ago
Amplify | Change runtime for deployasked 5 months ago
Problems while hosting Remix JS app with AWS Amplifyasked 9 days ago
How to add domain alias to existing CloudFront distribution using CDKAccepted Answerasked 10 months ago
Adding new S3 bucket to existing distributionasked a year ago
Amplify can't deploy, stuck while deployingasked 2 years ago
How to protect AWS Amplify subdomains using AWS Shieldasked 2 months ago
Changing S3 Bucket Region of Aws Amplifyasked 3 months ago
Can a CloudFront origin be another CloudFront distribution?asked 6 months ago