SES will only send from an address or domain you have proved you own. This article creates that proof.

• An AWS account and the region chosen in “Get your Amazon SES access key”.
• Access to your domain’s DNS.

1. Open the Amazon SES console in your chosen region.
2. Choose Configuration > Identities. (AWS’s page also mentions a Get started wizard for first-time users.) The menu wording comes from AWS’s overview page and its general console steps, so confirm on screen.
3. Choose Create identity.
4. For a whole domain choose Domain and type it. Keep Easy DKIM on, which AWS says is default and recommended. You can set a custom MAIL FROM domain if you want. Choose Create identity.
5. SES shows three DKIM CNAME records. Each looks like token._domainkey.yourdomain.com pointing to token.dkim.amazonses.com.
6. Add those records at your DNS provider.
7. Wait. DNS can take time, and AWS says SES may take up to 72 hours to show the domain as verified.
8. To verify one address instead, choose Email address, enter it, and click the link in the message SES sends.
9. Use an address on that domain in Settings → VisionScaper Marketing → Send from address.

• It lets any address at that domain be used.
• It signs your mail with DKIM, which helps inbox placement.
• Gmail and Yahoo expect a DMARC record for bulk senders. Add one at your DNS host.

• If your account is still in the sandbox, you must also verify each recipient address (see the next article).
• Verification is per region. If you change region, verify again.

• Status stays pending. The CNAME names or values were copied wrongly. Some DNS hosts add your domain to the end of the name; enter only the host part.
• Mail still rejected. The From address uses a different domain than the one you verified.

• AWS, verified identities overview: https://docs.aws.amazon.com/ses/latest/dg/verify-addresses-and-domains.html (read 2026-10-15)
• The AWS page “Creating and verifying identities” was not opened. The console steps above are AWS’s general steps as summarized in the overview and should be checked on screen.

• Get your Amazon SES access key, secret key and region
• Move Amazon SES out of the sandbox
• Amazon SES SMTP credentials versus API keys