Open aaronrea opened 7 years ago
I like it. The SMS-Queuing-Client is in a good place. I am going to review these options and try to determine what is most viable. I also want to include CloudFormation templates for the architecture to see if we can get this turnkey.
1) Deploy stack(s). 2) Configure domain. 3) Install client. 4) Update client config with the domain.
as we discussed earlier.. this would be a good candidate for a serverless arch. I think the dataflow would be something like the following
curl -> API gateway -> lambda -> SNS
This will accomplish the simple case with no scheduling. If you wanted to time shift the messages you could probably use dynamodb to persist and either another lambda to poll or a scheduled lambda to move the message from dynamodb to SNS or SES. Either way you would need to pre-auth the receiver. I wonder if you can send email from lambda or if it is subject to the same port restrictions?
curl -> API gateway -> lambda -> dynamodb -> lambda -> SES/SNS
Thoughts?