Calendar Invite ETL - Lambda #1
How we eat the calendar invite data
Your customers will send calendar invites to a Universal AWS SES mailbox based on the AWS SES configuration you set up in your account.
In our case, we used create@calendarsnack.com for the calendarsnack domain.
The calendar invite data is copied and stored in S3 when sent to the configured AWS SES email box. The calendar invite data from the multipart message is broken down into components using a series of Lambdas.
Multi-Part Workflow
Step 1 - ETL Ingest - with Create@calendarsnack.com
Step 2 - Inject triggers Lambda #2 for ETL processing
Step 3 - Calendar Invite is sent using API#3 in the Landing Page or an Email List
Step 4 - Calendar Invite Data is collected, sorted, and stored for the event
