Email the contents of inbound AS2 messages
Receive AS2 messages from trading partners and have each decrypted payload delivered as an email attachment via Amazon SES. DocEvent runs the AS2 endpoint and returns the MDN receipt; your team just gets the document in their inbox.
From
AS2
To
SES Email
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Data Lakepull
Azure Filespull
Servers & protocols
FTP Pull
SFTP Pull
HTTP Upload
Email
Apps & trading partners
SharePointpull
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
Servers & protocols
FTP / FTPS
SFTP
Webhook
Email
Apps & trading partners
SharePoint
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.
How AS2 to SES Email routing works
Source
AS2
Files arrive from an AS2 trading partner over the internet — signed, encrypted, and acknowledged with an MDN receipt.
DocEvent Channel
routes · retries · logs
Destination
Email via SES
Files are delivered as email attachments via Amazon Simple Email Service.
1
File arrives via AS2
A hosted AS2 (RFC 4130) receive endpoint with its own URL — nothing to install and no AS2 server to run. Each source is pinned to one trading partner, so a message claiming any other AS2 identity is rejected, and the partner's certificate must verify every message. Encrypted payloads are decrypted and signatures verified automatically, and the MDN receipt is returned the way the partner asked for it: synchronously in the HTTP reply, asynchronously to their return URL, or not at all. Duplicate messages are detected per RFC 4130.
2
Channel routes it
DocEvent's channel server matches the incoming file to your configured route, queues it for delivery, and ensures no file is ever lost — even during downstream outages.
3
Delivered to SES Email
Amazon SES with configurable sender, recipient, subject, and body. Attachment included.
Common use cases
Real workflows that teams automate with a AS2 → SES Email channel.
- Send partner EDI documents to an operations mailbox as they arrive
- Notify a team with the attached document the moment an AS2 message lands
- Give a non-technical department visibility of AS2 traffic
- Forward inbound AS2 payloads to an accounts or logistics inbox
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the AS2 or SES Email side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
AS2
A hosted AS2 (RFC 4130) receive endpoint with its own URL — nothing to install and no AS2 server to run. Each source is pinned to one trading partner, so a message claiming any other AS2 identity is rejected, and the partner's certificate must verify every message. Encrypted payloads are decrypted and signatures verified automatically, and the MDN receipt is returned the way the partner asked for it: synchronously in the HTTP reply, asynchronously to their return URL, or not at all. Duplicate messages are detected per RFC 4130.
Files arrive from an AS2 trading partner over the internet — signed, encrypted, and acknowledged with an MDN receipt.Destination:
Email via SES
Amazon SES with configurable sender, recipient, subject, and body. Attachment included.
Files are delivered as email attachments via Amazon Simple Email Service.Automatic retries with exponential back-off
Full end-to-end audit log for every file
Zero-code setup via the DocEvent UI
Reliable delivery even during downstream outages
Related channel integrations
Other sources to SES Email
- Amazon S3 → SES Email
- HTTP Upload → SES Email
- Email → SES Email
- Filerouter (on-premise) → SES Email
- FTP Pull → SES Email
- SFTP Pull → SES Email
- S3 Compatible (pull) → SES Email
- GCS Blob Pull → SES Email
- Azure Blob Pull → SES Email
- Azure Data Lake Pull → SES Email
- Azure Files Pull → SES Email
- SharePoint → SES Email
- DocEvent Agent (on-prem) → SES Email