Reference · built on requestConnectorMessaging & notifications

Amazon Simple Email Service

Email sending, identities, configuration sets, and event publishing through the Amazon SES API v2.

Request accessPricing ↗

About

Amazon Simple Email Service is the email sending service in AWS. The SES API v2 has a regional endpoint per AWS Region and accepts Simple, Raw, or Templated messages at SendEmail (POST /v2/email/outbound-emails), returning a MessageId. Quotas are per Region and per account: sandbox accounts send 200 messages per 24 hours at 1 per second until production access is granted. Delivery outcomes are not returned in the call; they are published as events from a configuration set to CloudWatch, Data Firehose, EventBridge, Pinpoint, or SNS.

Through Fibric, an operator reads those published events and the account-level suppression list, then proposes a send, a bulk send, or a suppression change for a person to approve.

This is a reference listing. It documents what Fibric would read from Amazon Simple Email Service and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Sending events (Send, RenderingFailure, Reject, Delivery, Bounce, Complaint, DeliveryDelay, Subscription, Open, Click) published by a configuration set to an SNS topic, EventBridge, or Data Firehose
  • Message tags on each event: the EmailTags you set plus auto-tags such as ses:configuration-set and ses:from-domain
  • Addresses on the account-level suppression list, with reason BOUNCE or COMPLAINT, through ListSuppressedDestinations and GetSuppressedDestination
  • Sending identities through ListEmailIdentities and GetEmailIdentity
  • Account details through GetAccount
  • Per-message and metric data through GetMessageInsights and BatchGetMetricData where enabled

Proposed actions

  • Target capability: propose a Simple or Templated message through SendEmail, naming the ConfigurationSetName and EmailTags so its events are traceable
  • Target capability: propose a batch of templated messages through SendBulkEmail
  • Target capability: propose adding an address to the suppression list with PutSuppressedDestination, or removing one with DeleteSuppressedDestination
  • Target capability: propose a bulk suppression add or delete from an S3 object with CreateImportJob

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Backorder notices with delivery proof

    The operator proposes one templated message per delayed order through SendEmail with the order id as an EmailTag. Delivery and Bounce events arrive on EventBridge and update the order record.

    With Backorder Notice

  • Building shutdown notice to every tenant

    For a planned utility shutdown, the operator drafts the notice and proposes a SendBulkEmail to the tenant list. A person approves the wording and the send window once.

    With Shutdown Notice

  • Reminders that stop at a hard bounce

    A Bounce event with a hard bounce halts further reminders to that address. The operator proposes the next step, a call or a letter, and records why email stopped.

    With Dunning Cadence

Requirements

  • An AWS account with SES in your sending Region, out of the sandbox, so sends exceed 200 per 24 hours and suppression changes are allowed
  • A sending identity (address or domain) created with CreateEmailIdentity and confirmed, so it can appear as FromEmailAddress
  • A configuration set with an event destination (SNS, EventBridge, or Data Firehose) that Fibric can read, named on every send
  • An IAM role or user whose policy allows the sesv2 actions listed above and read access to the event destination
Authentication
AWS IAM credentials signing each request with Signature Version 4 (AWS4-HMAC-SHA256), limited to the sesv2 actions the role permits, against the SES endpoint of your Region.

Limits

  • A message takes at most 50 recipients and 40 MB after base64 encoding through API v2 or SMTP; messages above 10 MB are bandwidth-throttled
  • Every API action other than SendEmail, SendRawEmail, and SendTemplatedEmail is throttled at one request per second
  • Events publish only when the configuration set is named on the send; otherwise bounces and complaints are forwarded to the Return-Path or Source address
  • The suppression list is case-sensitive, records only hard bounces and complaints, and receives no complaint data from Gmail

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Amazon Simple Email Service ↗

Questions and answers

How do bounces and complaints reach Fibric?
Through event publishing. You create a configuration set with an event destination (SNS, EventBridge, Data Firehose, CloudWatch, or Pinpoint) and name the set in ConfigurationSetName on each send. Identity-level notifications by email or SNS topic also exist. Without either, SES forwards bounces and complaints to the Return-Path address.
What does the sandbox allow?
A sandbox account sends up to 200 messages per 24-hour period at 1 message per second. The account-level suppression list can be enabled, but PutSuppressedDestination and CreateImportJob are not available until the account has production access. Quotas apply per AWS Region.
What are the size and rate limits?
A message carries at most 50 recipients across To, CC, and BCC, and up to 40 MB after base64 encoding through API v2 or SMTP (10 MB through API v1). Non-sending actions are limited to one request per second. Sending rate and daily volume are adjustable quotas set for your account.
Ask about Amazon Simple Email Service

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Amazon Simple Email Service through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy