I have an application that runs fine in AWS App Runner and can be found here: https://iyarles.net

However, it’s not accessible via the naked domain name iyarles.net.
Clarification comment: If I goto iyarles.net in my browser (edge), the request times out. If I goto iyarles.net, my website loads fine.

The App Runner service has a custom domain configured and my hosted zone has the 2 certificate validation records and the alias record pointing to my service.

A few weeks ago I transferred my domain from Google Domains to Route 53. It was originally a redirect from iyarles.net or any other subdomain (with or without https://) to the default domain for my service.

How can I replicate the previous behavior? What exactly are these alias records doing?

>Solution :

When you type the hostname into the browsers address bar, browsers will assume you want to make a plain HTTP request.

When you explicitly include the https: scheme, browsers will make a secure HTTP request.

Your server is running an encrypted service on port 433. It is not running a plain service on port 80.

It times out if you type http://iyarles.net too.