Email evidence & lookup
Inbound email capture, content processing, metadata indexing, and an SSO-protected browser view.
The system at a glance.
A conceptual view of the flow and its boundaries.
The challenge.
Operational and customer-service teams need to inspect the actual email content associated with a communication, rather than infer it from a delivery record.
My contribution.
Owned the inbound capture infrastructure and worked across the supporting email processing and authenticated HTML retrieval experience.
Implementation.
- Provision SES identities, DNS records, receipt rules, and platform-specific SNS fan-out for three email platforms.
- Store content in encrypted S3 and index email metadata in DynamoDB with time-based indexing and expiration.
- Use separate platform processors to extract MIME/header metadata and prepare retrievable content.
- Serve stored HTML and meaningful HTML error responses through a read-only Lambda behind an OIDC-authenticated internal ALB.
Design decisions.
Separate metadata and content storage keeps lookups small while retaining rich email bodies in object storage.
An internal SSO boundary and read-only storage access simplify the retrieval service's authorization and mutation model.
Validation.
Infrastructure checks validate configuration; unit and acceptance tests cover the lookup path and HTML responses.
The outcome.
Established a traceable path from inbound email evidence to an authenticated browser-rendered view.
Explore the pattern.
The companion repository is an independent educational demonstration built with synthetic examples. It illustrates related engineering patterns and does not contain employer source code or production data. Repositories are currently private; please contact me for access.
Open private GitHub demo