How to use a Righthand with Amazon SES

Quick answer

Use Righthand to prepare an Amazon SES delivery-evidence report for an approved transactional batch. Send acceptance and delivery events must remain different states.

Start with a reviewable deliverable, keeping Amazon SES as the accepted home for its records. This guide uses an explicitly approved snapshot or browser read; it does not assume that every provider API action is exposed by your Righthand connection.

Evidence and access

AWS documents SES send, delivery, bounce, complaint, rendering-failure, and delay events. See the official Amazon SES reference. Provider capabilities and Righthand's available tools are separate checks.

Use the approved message and event receipts with message IDs, sending identity, timestamps, and event definitions. Do not grant new send authority. Verify the required tools and owner-approved scope through Righthand integrations; use the supplied packet when a native read is unavailable.

Define the objects and authority

Include these fields in the working input: message ID, configuration set, recipient reference, event type, event time, batch reference. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

A send event means SES will attempt delivery; delivery is to the recipient mail server, not proof of inbox placement or reading. No new sends are authorized.

Illustrative first-run brief

Use the owner-provided Amazon SES snapshot or approved read-only view. Review the supplied events for twenty approved notifications. Separate accepted, delivered, delayed, and failed outcomes. Prepare unresolved-item questions without resending. Run once for the agreed sample, using America/Los_Angeles for the review deadline and preserving source timestamps separately. Return the draft in this conversation by Friday at 3 PM Pacific for the messaging operator to review. Include source references and missing fields. Do not write records, spend money, change permissions, or send external messages. Stop and report an unavailable source rather than substituting another account.

Expected result and verification

A message with only a send event remains unconfirmed delivery. A bounce is a specific failure, not simply no reply.

Match message IDs and final observed events to the original event stream with the same batch filters. Record the source cutoff, applied filters, and items excluded from the sample. The reviewer should be able to follow each consequential finding back to an original object. A well-written summary is not evidence that a proposed action happened. If a later write is authorized, verify its specific result separately before changing the task's status.

Illustrative input and draft output

These synthetic entries show the requested review, not live account results or a provider field schema.

Common failure and recovery

Delayed or missing events can leave uncertainty. Reconcile the affected message before retrying and preserve unknown outcomes.

If a message has only submission evidence, label recipient delivery unverified and ask the owner for the relevant event receipt before changing status.

FAQ

What should the reviewer verify first?

Verify message ID, sender identity, event chronology, and recipient-specific evidence. Submission, delivery events, and a person's reading or response are different outcomes.

How should a repeat run be scoped?

Preserve message IDs and event windows across reviews. Reconcile retries before any separately authorized send so a missing event does not cause duplicate outreach.

For connection and permission details, use Righthand Docs. Review Pricing alongside any separate provider charges before expanding the workflow.