I have a problem verifying my request for aws certificate.

I'm sorry to hear you're having trouble verifying your AWS certificate request, Pat. Let's go through some steps to help resolve this issue:

1. DNS Verification: If DNS verification failed, it's possible there were issues with the CNAME record setup. Make sure the CNAME record was added exactly as provided by AWS Certificate Manager (ACM), including any underscores or periods. Some DNS providers don't allow underscores in CNAME values, so you might need to remove the underscore from the value (but keep it in the name) for validation.

2. Email Verification: For email verification, ensure you have access to one of the common administrative email addresses for your domain (admin@, administrator@, webmaster@, hostmaster@, or postmaster@). Check your spam folder in case the verification email was filtered.

3. Pending Status: ACM typically attempts to validate a domain for up to 72 hours. If validation fails within this period, the certificate status changes to "Validation timed out."

4. Public DNS: Ensure your domain is publicly resolvable. ACM requires that the domain records be accessible over the public internet.

5. CAA Records: Check if there are any Certification Authority Authorization (CAA) records that might be blocking the certificate issuance.

6. New Request: Since both attempts have failed, you should create a new certificate request. When doing so, double-check all details and choose your preferred validation method.

7. DNS Propagation: Remember that DNS changes can take some time to propagate. Allow some time after making any changes before requesting a new certificate validation.

If you continue to experience issues after trying these steps, you may need to contact AWS support for further assistance. They can provide more specific guidance based on your account and certificate details.

Remember, maintaining the correct DNS records (for DNS validation) or access to administrative email addresses (for email validation) is crucial for both initial verification and automatic certificate renewal.
Sources
Unable to request a Certificate in AWS | AWS re:Post
AWS Certificate verification pending | AWS re:Post
Subject: Issue with Pending Validation for SSL Certificate on AWS | AWS re:Post
Troubleshoot certificate validation - AWS Certificate Manager

It's strongly recommended against to use email verification. Stick with DNS verification. It gives major benefits, the most important one of which is the fully automated, "set it and forget it" style renewal of the certificate for as long as it's used by some resource (like a load balancer or CloudFront distribution) and the CNAME authorisation remains in place.

When you add the CNAME record in DNS, you need to copy the name of the record and particularly its value exactly as they are provided by ACM. Don't remove the trailing dot from the value, for example. ACM will poll for the record continuously and typicaly detects when it's properly in place in a few minutes. The CNAME name and value will remain the same on subsequent attempts, and it's the same for the entire account, regardless of which region you request the certificate in.

If the certificate isn't being issued, use a tool like nslookup or dig to query the CNAME record name (exactly as shown in the ACM console), and verify that the value returned exactly (including dots) matches the value shown in the ACM console. This is exactly the same test that ACM does, so as long as the values match, the certificate will be issued, unless there's a CAA record in the zone blocking ACM from doing so.