Issues DNSs configuration

Based on your description and the image of your DNS records, it appears you're experiencing a nameserver mismatch between your Route 53 domain registration and your hosted zone. This is a common issue when transferring domains to AWS.

When you transfer a domain to Route 53, you need to ensure that the nameservers in your domain registration settings exactly match those provided by Route 53 for your hosted zone. From your image, I can see you have DNS records set up in your hosted zone, but the domain might still be using the old nameservers from IONOS.

Here's how to fix this issue:

1. Check the nameservers assigned to your hosted zone in Route 53. These are the NS records you can see in your screenshot.

2. Go to the Registered Domains section in Route 53 and verify that the nameservers listed for your domain (logos360.net) exactly match those in the hosted zone.

3. If there's a mismatch (which is likely the case since your domain is "pending validation"), update the nameservers in the domain registration to match those in the hosted zone.

The "pending validation" status typically means that AWS is waiting for you to complete certain verification steps, which often includes confirming ownership through DNS records. Since you've transferred from IONOS, you need to make sure the domain is now using AWS nameservers instead of the previous provider's.

After updating the nameservers, it may take up to 24-48 hours for the changes to fully propagate globally, though it often happens much faster with Route 53.

You can verify your DNS configuration using the "dig" command to check if your domain is resolving correctly:

dig logos360.net

This will show you which nameservers are currently authoritative for your domain.
Sources
Route 53 owned domain is not being resolved | AWS re:Post
Domain records not verified | AWS re:Post
Troubleshoot DNS propagation issues that occur after a domain transfer. | AWS re:Post
Migrated domain to AWS and DNS not working in many places | AWS re:Post