Containers

There are two implementation options.

  1. On a local host, i.e., a PC.

  2. On a cloud computer as a serverless lambda.

Local Host

On a local host, i.e, a PC, the configuration looks like this:

https://www.plantuml.com/plantuml/svg/PL5B2eCm4Dtd54DNxS8Rb6Bfhfj2fGSOpLY5c94a8b9wzuu_r9f52EytRqZi0xhGL4Ofovh0S8O6FWhaP5pLRCa6gBjGiFq3So9DpX7AFL2Z2gBeikSq1apH4nIb3-ow0SpP20-7bbAeyKt-0EYX2D9cEofrt7f9-eubhuzNSfjAvgKXU2Q9SCSJK8MbhB8UF_Jf1HlmtADpbvryZDd1GpE5cPZWpespQ2H1gUNTvqxkgVDYNAbwRDv9nMIrVC0F

This requires either manually running the application periodically, or leaving it running in a terminal window.

Cloud

When using a cloud implementation, the configuration looks like this:

https://www.plantuml.com/plantuml/svg/PP9DJyCm38Rl-HLcuW27QOTTgshJn0M1G4I8izjwNQLyL4cg2X3_7JSqRLTwIABuyUitTWy-e0kTLkAcCQNgAe8CUxyhhTRMvAjR6Qp3cdP7ZL_MoFrqM8CdgzikCFWXdr0N5SwdDVfCtcFTc3g9FSZvb0k19HU5HzivWwhnGGXZEVVr1Dy2-6EdhJLa0XJEzfwS-1cHuykxJDIvKGHlKWx1Kjck0ZOqnYAieZd8ijlPQJu2rsNEH1KvHyXh3BFai5KOi41F8FSGTL9lbZ8JTE6dMFSv1SvMiHviUYgWvHxx3Q27I-39Z3NYxgWCQ6f-37TdKOLRjInpTm-aiKcvdBrq3Tjj7fjnTPaDjydM2kV8dzu_cUXGpECPP4PsdCUCBIY6qhZ4WKp5V-0l

This runs independently.

AWS cloud infrastructure requires a Cloud Formation Template to build the resources:

  • The S3 bucket.

  • The Lambda.

Also, the email domain information must be verified with Amazon to permit sending email. This means setting up an “me.admin@gmail.com” address in addition to “me@gmail.com”. A verification email must be sent and confirmed by AWS.

Further, the lambda must be configured with the ARN (Amazon Resource Name) for the S3 bucket.

Summary

Note that the components are the same. The host processing each component is distinct.