KosmoKrator

email

Amazon SES CLI for AI Agents

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.

6 functions 4 read 2 write Bearer token auth

Amazon SES CLI Setup

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 --json
kosmokrator integrations:doctor amazon-ses --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then use the same stored profile from scripts, coding CLIs, Lua code mode, and the MCP gateway.

KeyEnv varTypeRequiredLabel
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.

kosmo integrations:call amazon-ses.amazonses_send_email '{
  "from_email_address": "example_from_email_address",
  "destination": "example_destination",
  "subject": "example_subject",
  "html_body": "example_html_body",
  "text_body": "example_text_body",
  "template_name": "example_template_name",
  "template_data": "example_template_data",
  "reply_to_addresses": "example_reply_to_addresses"
}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:amazon-ses amazonses_send_email '{
  "from_email_address": "example_from_email_address",
  "destination": "example_destination",
  "subject": "example_subject",
  "html_body": "example_html_body",
  "text_body": "example_text_body",
  "template_name": "example_template_name",
  "template_data": "example_template_data",
  "reply_to_addresses": "example_reply_to_addresses"
}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

kosmo integrations:docs amazon-ses --json
kosmo integrations:docs amazon-ses.amazonses_send_email --json
kosmo integrations:schema amazon-ses.amazonses_send_email --json
kosmo integrations:search "Amazon SES" --json
kosmo integrations:list --json

All CLI Functions

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.

Parameters
from_email_address, destination, subject, html_body, text_body, template_name, template_data, reply_to_addresses, configuration_set_name

Generic CLI call

kosmo integrations:call amazon-ses.amazonses_send_email '{"from_email_address":"example_from_email_address","destination":"example_destination","subject":"example_subject","html_body":"example_html_body","text_body":"example_text_body","template_name":"example_template_name","template_data":"example_template_data","reply_to_addresses":"example_reply_to_addresses"}' --json

Provider shortcut

kosmo integrations:amazon-ses amazonses_send_email '{"from_email_address":"example_from_email_address","destination":"example_destination","subject":"example_subject","html_body":"example_html_body","text_body":"example_text_body","template_name":"example_template_name","template_data":"example_template_data","reply_to_addresses":"example_reply_to_addresses"}' --json

amazon-ses.amazonses_get_template

Read read

Retrieve an email template from Amazon SES by its name. Returns the template subject, HTML body, and text body.

Parameters
name

Generic CLI call

kosmo integrations:call amazon-ses.amazonses_get_template '{"name":"example_name"}' --json

Provider shortcut

kosmo integrations:amazon-ses amazonses_get_template '{"name":"example_name"}' --json

amazon-ses.amazonses_list_templates

Read read

List all email templates in Amazon SES. Returns template names and creation timestamps. Supports pagination.

Parameters
page_size, next_token

Generic CLI call

kosmo integrations:call amazon-ses.amazonses_list_templates '{"page_size":1,"next_token":"example_next_token"}' --json

Provider shortcut

kosmo integrations:amazon-ses amazonses_list_templates '{"page_size":1,"next_token":"example_next_token"}' --json

amazon-ses.amazonses_create_template

Write write

Create a new email template in Amazon SES. Templates can include HTML and plain text content with optional substitution variables (e.g., {{name}}).

Parameters
template_name, subject, html_content, text_content

Generic CLI call

kosmo integrations:call amazon-ses.amazonses_create_template '{"template_name":"example_template_name","subject":"example_subject","html_content":"example_html_content","text_content":"example_text_content"}' --json

Provider shortcut

kosmo integrations:amazon-ses amazonses_create_template '{"template_name":"example_template_name","subject":"example_subject","html_content":"example_html_content","text_content":"example_text_content"}' --json

amazon-ses.amazonses_list_suppressions

Read read

List email addresses on the suppression list for a specific configuration set in Amazon SES. Suppressed addresses will not receive emails.

Parameters
configuration_set, page_size, next_token

Generic CLI call

kosmo integrations:call amazon-ses.amazonses_list_suppressions '{"configuration_set":"example_configuration_set","page_size":1,"next_token":"example_next_token"}' --json

Provider shortcut

kosmo integrations:amazon-ses amazonses_list_suppressions '{"configuration_set":"example_configuration_set","page_size":1,"next_token":"example_next_token"}' --json

amazon-ses.amazonses_get_current_user

Read read

Get the currently authenticated user for the Amazon SES integration. Useful for verifying credentials and account information.

Parameters
none

Generic CLI call

kosmo integrations:call amazon-ses.amazonses_get_current_user '{}' --json

Provider shortcut

kosmo integrations:amazon-ses amazonses_get_current_user '{}' --json

Function Schemas

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.

Operation
Write write
Schema command
kosmo integrations:schema amazon-ses.amazonses_send_email --json
ParameterTypeRequiredDescription
from_email_address string yes The sender email address (must be verified in SES). e.g., "[email protected]" or "Sender Name <[email protected]>".
destination object yes Recipient addresses. Object with "ToAddresses" (array), "CcAddresses" (array, optional), and "BccAddresses" (array, optional).
subject string no The email subject line. Required unless using a template.
html_body string no HTML content of the email body.
text_body string no Plain text content of the email body.
template_name string no Name of an existing SES email template to use. If provided, subject/html_body/text_body are ignored.
template_data object no Key-value pairs to substitute into the template placeholders.
reply_to_addresses array no List of email addresses for reply-to.
configuration_set_name string no The SES configuration set to associate with this email for tracking and analytics.

amazon-ses.amazonses_get_template

Retrieve an email template from Amazon SES by its name. Returns the template subject, HTML body, and text body.

Operation
Read read
Schema command
kosmo integrations:schema amazon-ses.amazonses_get_template --json
ParameterTypeRequiredDescription
name string yes The name of the email template to retrieve.

amazon-ses.amazonses_list_templates

List all email templates in Amazon SES. Returns template names and creation timestamps. Supports pagination.

Operation
Read read
Schema command
kosmo integrations:schema amazon-ses.amazonses_list_templates --json
ParameterTypeRequiredDescription
page_size integer no Maximum number of templates to return per page (default: 10, max: 100).
next_token string no Pagination token from a previous response to fetch the next page of results.

amazon-ses.amazonses_create_template

Create a new email template in Amazon SES. Templates can include HTML and plain text content with optional substitution variables (e.g., {{name}}).

Operation
Write write
Schema command
kosmo integrations:schema amazon-ses.amazonses_create_template --json
ParameterTypeRequiredDescription
template_name string yes A unique name for the template.
subject string yes The email subject line. Supports substitution variables (e.g., "Welcome, {{name}}!").
html_content string no HTML body of the template. Supports substitution variables using {{variable}} syntax.
text_content string no Plain text body of the template. Supports substitution variables using {{variable}} syntax.

amazon-ses.amazonses_list_suppressions

List email addresses on the suppression list for a specific configuration set in Amazon SES. Suppressed addresses will not receive emails.

Operation
Read read
Schema command
kosmo integrations:schema amazon-ses.amazonses_list_suppressions --json
ParameterTypeRequiredDescription
configuration_set string yes The configuration set name to retrieve suppressions for.
page_size integer no Maximum number of suppressed addresses to return per page.
next_token string no Pagination token from a previous response to fetch the next page of results.

amazon-ses.amazonses_get_current_user

Get the currently authenticated user for the Amazon SES integration. Useful for verifying credentials and account information.

Operation
Read read
Schema command
kosmo integrations:schema amazon-ses.amazonses_get_current_user --json
ParameterTypeRequiredDescription
No parameters.

Permissions

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.