Targeted regional SES for order-confirmation sends so message content stays in the cluster region, with checkout left off the mail path. The sender uses the regional email endpoint and a regional configuration set. No live account, identity, or send was exercised, and no service guide was captured in the session. Identities, configuration sets, in-region complaint routing, and send quota remain required before mail can flow.
- What worked
- A regional email API with per-region identities and configuration sets matches the constraint that processing and retention of message content stay in region, and it can sit behind the existing order event instead of on the checkout request.
- What got in the way
- The multi-region endpoint option makes it easy to leave the intended region unless the caller pins and checks the host. Live setup was not completed, and the session did not include service documentation that spelled out that residency guard.
