---
title: What is the AWS SES Endpoint? | SendHQ
description: Find the correct AWS SES endpoints for API requests and SMTP configurations based on your AWS region and connection method.
canonical: https://sendhq.cc/terms/what-is-the-aws-ses-endpoint
last-updated: 2026-08-26
---
# What is the AWS SES Endpoint?

The AWS SES endpoint depends on the region where your account is hosted and the method of connection. For API requests, the endpoint follows the format email.region.amazonaws.com. For SMTP, the endpoint follows the format email-smtp.region.amazonaws.com. You must use the endpoint corresponding to the region where you verified your identities.

## API Endpoints

AWS SES API endpoints are region specific. For example, if your SES identity is configured in US East (N. Virginia), the endpoint is email.us-east-1.amazonaws.com. If configured in US West (Oregon), use email.us-west-2.amazonaws.com. These endpoints are used for HTTPS requests via the AWS SDK or CLI to manage identities, send emails, and configure receiving rules.

## SMTP Endpoints

SMTP endpoints are used for sending mail via the Simple Mail Transfer Protocol. The format is email-smtp.region.amazonaws.com. For example, the US East (N. Virginia) SMTP endpoint is email-smtp.us-east-1.amazonaws.com. These endpoints support standard SMTP authentication and are typically accessed via ports 25, 465, or 587 depending on the TLS configuration used.

## Region Selection

You cannot send email through an endpoint in a region where you have not verified your domain or email address. If you attempt to use an endpoint from a different region, the API will return an InvalidParameterValue or similar error. Always ensure your application configuration matches the region where your SES production access was granted.

## Connection Security

When connecting to SES endpoints, AWS requires secure connections. For SMTP, this means using STARTTLS or implicit TLS. For API calls, HTTPS is mandatory. Developers can use SendHQ free tools (https://sendhq.cc/tools) to verify that their DNS records like SPF and DKIM are correctly aligned with their SES configuration to ensure delivery.

## Endpoint Troubleshooting

If you encounter connection timeouts, verify that your network allows outbound traffic on the chosen port. Port 25 is often blocked by cloud providers to prevent spam. Use port 587 for STARTTLS or port 465 for implicit TLS. Ensure your AWS IAM credentials have the ses:SendRawEmail or ses:SendEmail permission for the specific region endpoint.

## Questions teams ask

**Can I use a global endpoint for AWS SES?**

No, AWS SES does not provide a single global endpoint. You must specify the regional endpoint where your identities are verified.

**Which port should I use with the SES SMTP endpoint?**

Use port 587 for STARTTLS or port 465 for implicit TLS. Port 25 is available but frequently blocked by ISPs and cloud providers.

**How do I find my specific SES region?**

Check the AWS Management Console under the SES dashboard. The region is indicated in the top right corner of the console or in the URL.

**What happens if I use the wrong endpoint?**

The request will either fail to connect or return an error stating that the identity is not verified in that specific region.

## Primary sources

- [Amazon SES Developer Guide](https://docs.aws.amazon.com/ses/latest/dg/) — Amazon Web Services
- [Service Name and Transport Protocol Port Number Registry](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml) — IANA

## Continue learning

[amazon ses](https://sendhq.cc/guides/amazon-ses.md) [amazon ses api](https://sendhq.cc/guides/amazon-ses-api.md) [aws ses service](https://sendhq.cc/guides/aws-ses-service) [smtp port](https://sendhq.cc/guides/smtp-port.md) [smtp relay service](https://sendhq.cc/guides/smtp-relay-service.md)