a.ardentunited.me. 1799 IN A 34.217.34.181
a.ardentunited.me. 0 IN CNAME _705a3fba37c159e591bcd76735b90c5f.acm-validations.aws.
a.ardentunited.me. 1799 IN TXT "28bGXnTHCkwBj5Pso3VrsqOLNvbin99PZupYBZ9NEmA"
Please keep in mind that you can’t mix CNAME records with any other record type. The presence of that CNAME is possibly disabling your A record.
I do not think AWS asked you to create that record. Their instructions usually provide a label that begins with an underscore. A wildcard CNAME like that is a surefire way to screw up your zone.
Another thing to consider is that *.example.org does not cover example.org on its own.
What you should do is just create separate records for your zone apex (example.org and www.example.org).
Looks fine now, but you’ll probably need to wait out the DNS cache on your local workstation and whatever resolvers you are using, before that browser error is gone.
Your server doesn’t seem to actually be accessible on ports 80 or 443, though.
That’s the issue, you haven’t have nginx reading vHosts from sites-enabled folder.
Go to your nginx.conf file located in /etc/nginx/nginx.conf, add the line include /etc/nginx/sites-enabled/*; (change the directory to where the sites-enabled actually located) to the bottom of the file (last line)
Couldn't restart.
Job for nginx.service failed because the control process exited with error code. See "systemctl status nginx.service" and "journalctl -xe" for details.