Skip to main content

​
Prerequisites

You can use API or SMTP credentials. To learn more, see Amazon’s Using Credentials With Amazon SES.

​
Configure Amazon SES with API credentials

  1. Log in to your Amazon AWS account.
  2. Verify your domain.
  3. Verify email addresses
  4. Request production access.
  5. Get your AWS access keys. Copy these keys; you will need to enter these values into Auth0.
  6. Attach a policy with the proper permissions. Attach a policy with the ses:SendRawEmail and ses:SendEmail permissions, as in this example: 
    {
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "ses:SendRawEmail",
                "ses:SendEmail"
            ],
            "Resource": "*"
        }
    ]
}
  7. Navigate to Auth0 Dashboard > Branding > Email Provider.
  8. Activate the Use my own email provider toggle.
  9. Click the Amazon Web Services logo.
  10. Provide a From email address, enter your AWS Access Key Id and Secret Access Key, select your Region.
  11. Click Save.

​
Configure Amazon SES with SMTP credentials

  1. Log in to your Amazon AWS account.
  2. Verify your domain.
  3. Request production access.
  4. Get your SMTP credentials. Copy the security credentials; you will need to enter these values into Auth0.
  5. Navigate to Dashboard > Branding > Email Provider.
  6. Activate the Use my own email provider toggle.
  7. Click the SMTP logo.
  8. Provide a From email address, then enter your SMTP server Host, Port, Username, and Password, and click Save. You can use email-smtp.us-east-1.amazonaws.com (using the appropriate region rather than us-east-1) for Host and 587 for Port.

​
Send a test email

Send a test email using the Send Test Email button. If the configuration is correct, you receive a confirmation email. If you do not receive an email after a few minutes, check your Auth0 logs for error codes. Once configured, the Amazon SES console displays delivery insights for all emails that have been sent to your users.