SES SMTP Email / SMTP Origin: Network OSI layer 7 · Application Last updated 18 Nov 2026

Amazon SES SMTP: 535 Authentication Credentials Invalid (IAM user vs SMTP credentials, region)

The SMTP login to SES fails because you used the wrong kind of credentials or the wrong regional endpoint.

Exact message you may see 535 Authentication Credentials InvalidSES SMTP 535 Authentication Credentials Invalidsmtplib.SMTPAuthenticationError: (535, b'Authentication Credentials Invalid')email-smtp.us-east-1.amazonaws.com 535Authentication Credentials Invalid Amazon SES
Seen on: AWS SES Python Email

Meaning

SES SMTP needs SMTP credentials derived from an IAM access key (not the access key ID/secret directly, and not the console password), generated for the same region as the endpoint (email-smtp.eu-west-1.amazonaws.com). Create them in SES → SMTP settings, or convert the secret with AWS's algorithm.

Common causes

  • Using the raw IAM secret instead of the SMTP password
  • Credentials created for another region
  • Wrong endpoint hostname
  • Special characters mangled in config
  • Deleted/disabled IAM user

⚡ Quick fix

  1. Generate SMTP credentials in the SES console for that region
  2. Use the matching email-smtp.REGION.amazonaws.com endpoint
  3. Paste credentials without whitespace

Detailed fix by platform

Shell

  1. bash
    # SES console > SMTP settings > Create SMTP credentials
    openssl s_client -starttls smtp -connect email-smtp.eu-west-1.amazonaws.com:587

How to diagnose

  1. Credentials — SMTP type?
  2. Region — Same?
  3. Endpoint — Correct?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

454 — 454 4.7.0 Temporary authentication failure (SMTP AUTH backend unavailable) (Email / SMTP)454530 5.7.0 Authentication Required — SMTP: 530 5.7.0 Must issue a STARTTLS command first / 530 5.7.1 Authentication required (Email / SMTP)530 5.7.0 Authenticat…534 5.7.9 Application-specific password required — SMTP: 534-5.7.9 Application-specific password required. Learn more at https://support.google.com/accounts/answer/185833 (Email / SMTP)534 5.7.9 Application…535 5.7.8 Username and Password not accepted — SMTP: 535-5.7.8 Username and Password not accepted. Learn more at https://support.google.com/mail/?p=BadCredentials (Email / SMTP)535 5.7.8 Username an…ACM region — CloudFront can't use my ACM certificate: it must be requested in us-east-1 (N. Virginia) (SSL / TLS)ACM regionALB listener — ALB HTTPS listener: CertificateNotFound / default certificate missing or SNI certificate list incomplete (SSL / TLS)ALB listenerAWS_CA_BUNDLE — AWS CLI/SDK: SSL validation failed for https://... certificate verify failed (custom CA bundle / proxy) (SSL / TLS)AWS_CA_BUNDLECNAME — CloudFront: CNAMEAlreadyExists / alternate domain name not covered by the certificate (InvalidViewerCertificate) (SSL / TLS)CNAMESES SMTP

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.