-2
It’s my first experience with AWS and it’s been really complicated. I have no domain for machine assembly, no DNS routing, and what I’ve achieved so far is creating an instance of Beanstalk, configuring the MYSQL database and uploading the site.
In the testing phase, the solution works without any fault.
Route 53 was configured, then NS’s information was recorded in Registro.br for domain propagation.
Route53 Dashboard - Configuration was done on both Url’s with and without www.
Result: No use of www., it works. With use of www. no return. And in no case did the SSL certificate generated by Certificate Manager work.
Certificate Manager panel, also created for the two URL’s own SSL certificates.
Using Dnschecker, I detected that the URL using www is directed to the old server (hostgator) of the site, there being the correct propagation to the new hosting server.
https://dnschecker.org/#A/www.mosteirodesaobento.com.br
How can I proceed? My client’s plan is BASIC and I don’t have the support.
I did this. In DNS Checker, it is pointing to the correct IP apparently. But when trying to access via browser, it gives timeout. Is it just the spread of DNS?
– Maykel Esser
DNS propagation would only impact IP resolution. Apparently the problem now is with Elasticbeanstalker. It has some configuration related to the certificate and Cnames?
– Mathias Berwig