misty depot
I have a Next.js project hosted on AWS Amplify. It was deployed to Amplify in January. It has been working without error, and has not been updated or re-deployed since.
The project uses Upstash to process background jobs https://upstash.com.
On Friday, 20 June, the App failed a background job in the middle of the process. And has been failing ever since. Looking at the Upstash logs I am getting a 403 ERROR.
403 ERROR, The request could not be satisfied. Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Thinking it was an Upstash issue, I reached out to their support. They did a deep dive and believe it is in fact an AWS Issue relating to the CloudFront configuration.
My Amplify setup is vanilla / all defaults. Loggin into Amplify I saw the (new) Firewall / WAF feature was available. Thinking this may have been the root cause enabled it. But I can confirm that with WAF enabled or disabled I am still getting the same 403 error.
The App does have a Custom Domain attached to it. But I can confirm that with a Custom Domain and without a Custom domain, I am still getting the same 403 error.
And again, I can confirm, since January there have been no changes to the code, no deployments and or configuration changes to the Amplify environment form my part. Has AWS made any changes in the background that has triggered this all of a sudden ?
Any ideas what may be causing this ?
raw grove
