docs(inbound-email): document AWS SES adapter across greenfield frameworks#8
Open
mpge wants to merge 1 commit intodocs/attachment-downloaderfrom
Open
docs(inbound-email): document AWS SES adapter across greenfield frameworks#8mpge wants to merge 1 commit intodocs/attachment-downloaderfrom
mpge wants to merge 1 commit intodocs/attachment-downloaderfrom
Conversation
…works
Third provider alongside Postmark + Mailgun. AWS SES receipt rules
publish to an SNS topic; host apps subscribe via HTTP and SNS POSTs
the envelope to the same /...webhook/email/inbound endpoint, with
?adapter=ses selecting the parser.
Each greenfield framework page (dotnet/spring/go/phoenix/symfony)
gains an "AWS SES" subsection under Provider setup with:
- SNS subscription URL and adapter label.
- How to handle the one-time SubscriptionConfirmation envelope —
the typed exception / tuple the parser returns + what the host
controller should do with SubscribeURL.
- Where to inject the X-Escalated-Inbound-Secret header when SNS
itself doesn't forward custom headers (infrastructure-level:
load balancer / API gateway / CDN / edge proxy).
- What receipt rule action + encoding to choose for full MIME
content delivery (action.type=SNS, encoding=BASE64), plus the
fallback behavior when the rule doesn't supply content
(metadata-only routing still works via threading).
_intro.md now lists SES alongside Postmark + Mailgun and the adapter
selector shows `postmark|mailgun|ses` in every framework row of the
webhook URL table.
Phoenix page additionally shows the updated :inbound_parsers list
that includes SESParser.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Third inbound provider alongside Postmark + Mailgun. AWS SES receipt rules publish to an SNS topic; host apps subscribe via HTTP and SNS POSTs the envelope to the same `/...webhook/email/inbound` endpoint with `?adapter=ses` selecting the parser.
Implementation PRs:
What's added
Each greenfield framework page (dotnet/spring/go/phoenix/symfony) gains an AWS SES subsection under Provider setup with:
`_intro.md` now lists SES alongside Postmark + Mailgun and the adapter selector shows `postmark|mailgun|ses` in every framework row of the webhook URL table.
Phoenix page also shows the updated `:inbound_parsers` list including `SESParser`.
Stacked PR
Based on `docs/attachment-downloader` (#7). Merge order: #6 → #7 → this PR.