2 Answers
- Newest
- Most votes
- Most comments
0
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?
answered 2 years ago
0
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?
answered 2 years ago
Relevant content
- Accepted Answerasked a year ago
- asked a year ago
- Accepted Answerasked a year ago
- asked 6 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 months ago