404 errors on path requests to React app on AWS s3 using react-router-dom
We have a react application hosted/deployed on AWS S3. It uses react-router-dom v6
When there is an error, I set it to go to index.html. The problem is that when moving like "xxx/admin" within React, there is actually only index.html in s3 (xxx/admin is not present), resulting in an error of 404. After that, when an error occurs, it is redirected to index.html and then called properly.
Please tell me how to get rid of this error. It's hard to find because it's my first aws.
I think before react.js bundle is imported, xxx/main request first and error redirect to index.html. when redirect to index.html, js imported so react will render the correct pages. if so, how do I fix this problem?
or
I think it's SPA, so only one index.html file exists, but when error occurs, AWS s3 called something that doesn't exist file. I want to know the fundamental solution rather than using cloudFront. (redirect error 404 -> 200).
Disclaimer: this is a solution using CloudFront.
In case it might help.
I encountered similar problems when I used react-router-dom v5 & v6. I used BrowserRouter. I deployed the React app directly to S3 without using AWS Amplify. I kept encountering 403 error instead of 404, although I rechecked all my permission settings.
This article helped me eventually: https://blog.nicera.in/2020/08/hosting-react-app-on-s3-cloudfront-with-react-router-404-fix/. And your questions raised here had been discussed and answered in details in this article.
Open up your CloudFront distribution for the React App. In the top tabs, click on Error Pages.
Add the configurations for 403 & 404 as below.
