There could be several reasons why your S3 static website is not accessible. Here are some things you can check:
Check if the S3 bucket is still accessible: Make sure the S3 bucket that contains your website's files is still accessible. You can try accessing it directly through the S3 console or by using the bucket's endpoint URL. If you can't access the bucket, it's possible that the bucket policy or the access control list (ACL) has been modified, which can result in the bucket becoming inaccessible.
Check if the Route 53 record is still pointing to the correct S3 bucket: Make sure the Route 53 record that maps your domain name to the S3 bucket is still pointing to the correct bucket. You can check this by going to the Route 53 console and checking the record's settings. If the record is pointing to the wrong bucket, update it to point to the correct bucket.
Check if the domain name has expired: If you purchased your domain name from a registrar, make sure the domain name has not expired. If it has, you will need to renew the domain name.
Check if the SSL certificate has expired: If you are using SSL/TLS to encrypt traffic to your website, make sure the SSL certificate has not expired. If it has, you will need to renew the SSL certificate.
Check if there are any issues with your internet connection: Sometimes, issues with your internet connection can prevent you from accessing websites. Try accessing your website from a different device or network to see if the issue is with your internet connection.
If none of these steps resolve the issue, you may need to provide more information about your setup to troubleshoot the issue further.
Please let me know if that helped
Did I answer your question? please let me know
- Accepted Answerasked a year ago
- Accepted Answerasked 3 months ago
- Why isn't my domain record in Route 53 that points to an Amazon S3 bucket or static website resolving?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 3 months ago
- EXPERTpublished 4 months ago
It might help in finding the problem if you could tell what is the URL for the website you have.