Use the Amazon SES CLI from KosmoKrator to call Amazon SES tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.
Amazon SES can be configured headlessly with `kosmokrator integrations:configure amazon-ses`.
# Install KosmoKrator first if it is not available on PATH.curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash# Configure and verify this integration.kosmokrator integrations:configure amazon-ses --set access_token="$AMAZON_SES_ACCESS_TOKEN" --enable --read allow --write ask --jsonkosmokrator integrations:doctor amazon-ses --jsonkosmokrator integrations:status --json
Credentials
Authentication type: Bearer tokenbearer_token. Configure credentials once, then use the same stored profile from
scripts, coding CLIs, Lua code mode, and the MCP gateway.
Key
Env var
Type
Required
Label
access_token
AMAZON_SES_ACCESS_TOKEN
Secret secret
yes
Access Token
url
AMAZON_SES_URL
URL url
no
SES API URL
Call Amazon SES Headlessly
Use the generic call form when another coding CLI or script needs a stable universal interface.
Every function below can be called headlessly. The generic form is stable across all integrations;
the provider shortcut is shorter but specific to Amazon SES.
amazon-ses.amazonses_send_email
Write write
Send an email via Amazon SES. Specify the sender, recipient(s), subject, and body (HTML and/or plain text). Optionally reference a template or add reply-to addresses.
Use these parameter tables when building CLI payloads without calling integrations:schema first.
amazon-ses.amazonses_send_email
Send an email via Amazon SES. Specify the sender, recipient(s), subject, and body (HTML and/or plain text). Optionally reference a template or add reply-to addresses.
Headless calls still follow the integration read/write permission policy. Configure read/write defaults
with integrations:configure. Add --force only for trusted automation that should bypass that policy.