SES alerts
Send kwatch incident alerts to SES. Use the interactive manager for installation and credential setup. This page explains the provider fields and shows a minimal configuration fragment.
Before you start, have these values ready:
accessKeyId— AWS access key ID.secretAccessKey— AWS secret access key.from— Verified sender address.to— Recipients (comma-separated).
Credentials, tokens, keys, passwords, and webhook URLs must be mounted
from a Kubernetes Secret. Use an exact ${file:/absolute/path} reference
for every field marked Secret.
Configuration
| Field | Type | Required | Secret | Validation | Default | Description |
|---|---|---|---|---|---|---|
accessKeyId | string | yes | yes | — | — | AWS access key ID |
secretAccessKey | string | yes | yes | — | — | AWS secret access key |
region | string | no | no | — | us-east-1 | AWS region (default: us-east-1) |
from | string | yes | no | — | — | Verified sender address |
to | string | yes | no | — | — | Recipients (comma-separated) |
subject | string | no | no | — | — | Email subject |
routes | json | no | no | json | — | Optional JSON route filters. |
retry.maxAttempts | integer | no | no | integer | — | Optional maximum retry attempts. |
retry.delay | string | no | no | — | — | Optional retry delay, for example 5s. |
fallback | string | no | no | — | — | Optional fallback provider name. |
Minimal example
alert:
ses:
accessKeyId: "${file:/config/ses-accessKeyId}"
secretAccessKey: "${file:/config/ses-secretAccessKey}"
from: <from>
to: <to>
Add routes, retry, and fallback when you need delivery filtering or recovery. See the channels overview for guidance, or the complete provider reference for the catalog-wide view.