We are moving our application from Next11 to Next13 and deploying to Amplify. Before this we were using a customized cloudfront and Serverless to take care of all our redirects as we need some path to go to different application behind an ALB. We want to keep that behavior with Amplify Next13 application seems fine but the redirects just show:
502 ERROR
The request could not be satisfied.
CloudFront wasn't able to connect to the origin. 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.
Generated by cloudfront (CloudFront)
We cannot find a way to customize that Cloudfront distribution as amplify is deploying a managed one that we are not able to access through our console or cli to edit.
Is there a way to modify the behaviors for the rewrites and redirects or at least to be able to use a custom Cloudfront distribution for our amplify deployment so we can change the cache policy on the behaviors to make the redirect work as with our previous environment?
AWS 공식업데이트됨 2년 전
