ECS runs batch data processing jobs and uploads results to OSS; EventBridge independently detects file arrivals in OSS, then fans out notifications via Twilio (SMS/WhatsApp) and Resend (branded email) to stakeholders, while closed-loop webhook ingestion captures delivery receipts, bounces, and open events back into the system for end-to-end auditability.
ECS runs batch data processing jobs and uploads results to OSS; EventBridge independently detects file arrivals in OSS, then fans out notifications via Twilio (SMS/WhatsApp) and Resend (branded email) to stakeholders, while closed-loop webhook ingestion captures delivery receipts, bounces, and open events back into the system for end-to-end auditability.
See _combos/event-driven-automated-email-notification-pipeli-38a7a1.
See _combos/event-driven-transactional-email-pipeline-d58f51.
See _combos/decoupled-batch-pipeline-with-event-driven-verif-27f69e.
See _combos/closed-loop-multi-channel-notification-pipeline-b18bac.
Q: How does the batch pipeline trigger multi-channel notifications and track delivery status after files are uploaded to OSS? A: The system uses EventBridge to detect file arrivals in OSS after ECS completes batch processing, which automatically fans out notifications via Twilio for SMS and Resend for branded email. A closed-loop webhook then captures delivery receipts, bounces, and open events back into the system to ensure end-to-end auditability.