browser cannot find server in the subdomain

Based on the error message you're seeing, there are several potential issues with your subdomain configuration:

1. The error "Safari can't find the server 'http'" suggests there's a URL formatting problem. It appears the browser is trying to access "https://http//example.info/index.html" which is malformed (notice the double protocol and missing colon).

2. For your www subdomain to work properly with CloudFront, you need to ensure:

• The www.example.info subdomain is added as an alternate domain name (CNAME) in your CloudFront distribution settings
• Your SSL/TLS certificate in AWS Certificate Manager covers both example.info and www.example.info
• You have a proper A record in Route 53 for www.example.info that points to your CloudFront distribution

3. For the CloudFront endpoint access issue, verify that your distribution is properly configured with the correct origin (your S3 bucket).

To fix these issues:

• Check your CloudFront distribution settings to ensure www.example.info is listed as an alternate domain name
• Verify your Route 53 configuration has an A record for www.example.info set as an alias to your CloudFront distribution
• Ensure your SSL certificate covers both the root domain and www subdomain
• Check that your origin settings in CloudFront correctly point to your S3 bucket website endpoint

DNS changes can take time to propagate (24-48 hours in some cases), so if you've recently made changes, you might need to wait for them to take effect.
Sources
My site doesn't shows up when using the domain name | AWS re:Post
Route 53 subdomain not working with CloudFront | AWS re:Post
Requests can't be served when sending requests to cloudfront alternate domain name | AWS re:Post

Hi, It seems that you've simply mistyped your 2nd url: the colon i.e. : is missing in http//example.info/index.html. That's why you get an error message including http in https://http//example.info/index.html: http is interpreted as 1st name segment of the url instead of as protocol information.

Also check that you have a definition for www.example.com in your DNS server: it can for example be an alias on head DNS name example.com

Best,

Didier

After thoroughly seeking information it was found out that on the www.mydomain.info bucket on the permissions tab on the Block public access (bucket settings) the public access was blocked. Simply unchecking the setting emerged into no more malformation and the site becoming visible.

Later Edit: later on seemingly the malformation emerged again... :)

Thank you all!