> For the complete documentation index, see [llms.txt](https://docs.shipped.club/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shipped.club/features/authentication/aws-ses.md).

# AWS SES

First, you’ll need to create your SMTP credentials for AWS Simple Email Service (SES):

* On the old SES console, there’s an **SMTP Settings** link on the left side.
* On the new SES console, the link is under **Account dashboard** on the left sidebar.

Create new SMTP credentials, and copy them. The final string will look like this:

```
smtp://username:password@email-smtp.us-east-1.amazonaws.com:587
```

There are three variables that you should replace in this string:

* `username` and `password`, which are the SMTP credentials you created earlier.
* `us-east-1` replace it with the region that you’re sending emails from

Set this value into the .env file

```yaml
AWS_SES_SMTP="smtp://username:password@email-smtp.us-east-1.amazonaws.com:587"
```

Open `src/config/auth.ts` and set:

```typescript
EmailProvider({
    server: process.env.AWS_SES_SMTP || ""
    from: process.env.EMAIL_FROM || "",
    // maxAge: 24 * 60 * 60, // How long email links are valid for (default 24h)
}),
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.shipped.club/features/authentication/aws-ses.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.