2 Answers
- Newest
- Most votes
- Most comments
0
Figured out it is because when adding the CNAME to enable the https, I missed the ending period in the name. Now. my custom domain is available. But it still doesn't work, it says 404.
answered 5 months ago
0
Checking if you include the '.' at the end, '.' mean that is FQDN and different with no '.' at the end. I have been faced with same situation before, please copy exactly given CNAME, and URL you got in Amplify console.
answered 4 months ago
Relevant content
- asked 2 years ago
- asked a year ago
- asked a month ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago