Step 1(A.) new calendar
invite event request/
get new event request
from email box –
SNS/SQS
Virtual Calendar Server is in a Serverless template in a private repo
Customers use their Calendar Client
to inject data into AWS by using
create, read, update and delete
commands of the calendar client to
remote control the calendar
invitation data into AWS serverless
stack. Final Calendar Invite Sends are
completed by using Embedded Web
Pages and Email Lists using your SES
account to send and track calendar
invites using the APIs.
Dynamo
DB
() Blue = SNS/SQS
() Green = Lambda
() Red = SES
= () Email
Templates
= (9) Grey API’s
=() Propriety Lambdas
= (1) Sam Template=
42 Assets
in SAM Template
Step 2 (A.) disassemble
Calendar Invite -get new
calendar invite from s3
email box to ETL to
Dynamo DB with UID
(Proprietary LAMBDA)
S3
Calendar Invite Data Into AWS
Your SES Account
[email protected]
4(A). GOOD new event
request/
create new event record
4(B). create new
Calendar invite
event record
5(C.) new event created/
notify organizer of
successful event created
8(f).notify organizer
of event
limited reached with
SES Message
7(A).event canceled/
cancel event from
organizer calendar
client
5(A). new bulk event
invitees from email/
get new bulk invites
from email
5(B).get new
bulk event
Invites from
email
5(C). send bulk
Calendar Invite event
to List
5(D).reassemble calendar invite - send bulk Calendar Invite using data from dissembled Step 2A
Lambda and insert into AWS RAW SES API to send the Calendar Invites from Web Pages or
Subscribed Email Lists (Proprietary LAMBDA)
3(B). notify organizer of failed event create with SES template of Fail
Calendar Invite Ingest into AWS with all the data to the organizer
7(B).cancel event7(C). event canceled complete/
Stage-attendees for canceled
event
7(D). Stage attendees
for canceled event
7(F). sent event
Canceled SES Message
7(E).New event cancel request/
Send event cancelation
8(B).update event 8(F). send Calendar Invite
update using SES UID Match8(D).Stage
attendees for
updated event
8(E).New event update request/
Send event update8(A).event updated/
update event from
organizer calendar client
3(C). SES email notification template
6(E) .SES
email
notification
template
API # -1-Single Event Details
API #-1-Single
Event Details
API # 3-Single Event Invitee List Send
API # 3-Single
Event Invitee
List
API # 3-Single
Event Invitee List
7(E). event limit
reached/
notify organizer of
event limit reached
6(D.) notify
organizer of
successful
event created with
SES Message
6(A).new event reply
from email/
get new event reply
from email box
6(B). get new
event reply
from calendar
invite receipts
6(D). update
event
attendee UID
record in Dynamo
(E). API #2- Single Event Statistics and Reporting
6(C). get new
event reply
from calendar
invite receipts
8(G).SES email
notification
templateor
7(G) .SES email
notification
template
3(A). FAIL event create/
notify organizer of FAILED
event create
8(C). event update
complete/
stage attendees for updated
event
STEP 1 STEP 2
3.
4.
5.
6.
7.
8.
Aug 23 2024
The Calendar Server Message Pipeline message flow
SEE - https://31events.com