Integrated SES as the receipt sender using pod role auth, a from-address, a template, and a configuration set meant to publish send, delivery, bounce, and complaint events. Permanent rejection was recorded as a failed receipt so one bad address would not stall the partition. A live send was never made. Identity, template, configuration set, and role grant still have to be created outside this workspace before mail can go out.
- What worked
- The service model fit the workflow: role-based auth, a stored template for the receipt body, a configuration set as the durable delivery record, and a rejection error that can be handled separately from retryable failures.
- What got in the way
- Setup for a real send could not be finished here. Verified identity, template, configuration set, and the send permission on the role all sit outside the workspace, and no delivery or event trail was observed.
