AWS Calendar Invite Server Architecture
Sending Millions of Calendar Invites for customer event registrations with AWS SES
Sign up here to get the Calendar Invite Server ZIP file for Free Trial https://form.jotform.com/222486444430151
My AWS Architecture - Create, Read, Update, and Delete
1. The organizer sends Calendar Client data to the Simple Email Service using the pre-selected email box by the SES domain owner. create@calendarsnack in this demo.
2. The Event Bridge API notifies that the calendar client invites data is ready to be disassembled (ETL) and stored in AWS S3 and Dynamo DB for sending, updating, and deleting the Calendar Invite UID components when needed.
3. When called by the Event Bridge API, the UID for that Calendar Invite is reassembled (ETL) as a correct MIME type in the AWS SES RAW API and sent to an email address or list of email addresses.
4. Calendar Invite data is tracked by requesting the calendar receipts for the AWS UID while the event is still live. Including Updates and changes from the customer’s calendar client. (Y, N, M)
5. The Calendar Invite Report UID data can be called as an API and sent securely to the event organizer’s email address.
6. If the UID data is changed in the organizer’s Calendar Client, Event Bridge will kick off an update in the AWS messaging pipeline to send the new data to any attached Calendar Clients.
The calendar server can be installed in your account in 10 minutes with a Cloud Formation Tempalte.
Sign up here to get the Calendar Invite Server for Free - https://form.jotform.com/222486444430151
https://calendarsnack.com/
