Amazon SES — add and edit

Add the connection in InboxMon

1. Sign in → Settings → ESP connections.
2. Provider: Amazon SES. Sending domain: the From domain (no www, no @).
3. Optional: DKIM selectors now, or save them later on the card.
4. Add connection. Copy the webhook URL (includes ?token=). Paste the whole string.

One card per ESP + sending domain. Each extra Add click creates a new URL. Only the URL you paste into the ESP will show Last event.

Add SNS and the SES configuration set

Reuse an existing SES card if you already have one for that domain. Do not Add connection again unless you need a new URL.

1. Copy the webhook from Settings (includes token).
2. AWS, same region as SES → SNS → Topics → Create topic. Type Standard. Example name: inboxmon-ses-events.
3. Create subscription: Protocol HTTPS, endpoint = that URL, Enable raw message delivery off. Status must become Confirmed (InboxMon auto-confirms; if not, open SubscribeURL in a browser).
4. Topic access policy must allow ses.amazonaws.com to publish.
5. SES → Configuration sets → create one (example name inboxmon) if you do not have it.
6. Event destination → Amazon SNS → that topic. Enable send, delivery, bounce, complaint, reject, delivery delay. Opens/clicks need engagement tracking on the set.
7. Every send must use the set: header X-SES-CONFIGURATION-SET: inboxmon or API ConfigurationSetName. On the identity, you can set it as the default configuration set.
8. Send a test. Mail without the set still sends; InboxMon sees nothing.

Edit the connection in InboxMon

You cannot rename the provider or sending domain on an existing card. Use the card controls:

• Copy — same webhook URL. Use this when you need to paste it again into the ESP.
• Disable — InboxMon stops ingesting. The ESP may still POST; those requests are skipped. Use this for unused duplicate cards.
• Enable — ingest resumes on the same URL. You do not get a new token.
• DKIM selectors → Save selectors — for the Domains watchdog only, not for webhook ingest. Gray placeholder text is not stored until you save.
• Sync ESP data / Sync now — re-runs DNS and anomaly detection on events already stored. It does not pull history from the ESP.

To change the sending domain, add a new connection, point the ESP at the new URL, then Disable the old card.

Edit the weblink in AWS

The InboxMon URL lives on the SNS HTTPS subscription, not in the SES identity screen.

Change the webhook URL (topic still exists)

1. InboxMon → Copy the URL from the existing card.
2. SNS → the topic → open the HTTPS subscription. You cannot edit the endpoint.
3. Delete that subscription.
4. Create subscription: HTTPS, new URL, raw message delivery off. Wait until Confirmed.
5. Leave the SES event destination pointed at the same topic if the topic ARN did not change.

You deleted the SNS topic

1. Create a new Standard topic in the same region.
2. Add an HTTPS subscription to the InboxMon URL (raw off) → Confirmed.
3. Allow SES to publish on the topic policy.
4. SES → Configuration sets → your set. Remove the broken SNS destination. Add destination → Amazon SNS → the new topic → same event types.
5. Keep sending with that configuration set. Send a test.

You deleted the configuration set

Recreate the set, add an SNS destination to the (new or existing) topic, and put the set back on the identity or on every send.

Pause ingest

Disable the InboxMon card, or remove/disable the SES event destination. Extra InboxMon SES cards with No events yet: Disable them — they are unused URLs.

Confirm it works

Send a real message. Within about 30 seconds the card should show Last event, then Overview and Events fill in. Keep the webhook URL private. Requests without a matching token return 401. A full monthly event cap returns 429.

If Last event stays empty

• This card’s URL is the SNS HTTPS endpoint (token included).
• SNS subscription Confirmed, raw delivery off.
• Configuration set is on the send (or default on the identity).
• Connection active.