Skip to main content

A Serverless Application on AWS


By Morgan Lucas, From Adrian Cantrill’s More Than Certified / GitHub. Find the Notion Page HERE.

Pictured: Someone who would get use out of the app.

Technologies used: AWS, Lambda, Step Functions, API Gateway, S3, SNS & SES.

What Is This?:

A small app for pets to both you for cuddles that will send an alert to a phone and an email address. Both points of contact must be opted into first.

Stage 1

  • I register 4 objects - Two email addresses (sending messages, receiving messages) and 2 phone numbers (one to receive SMS [text messages], and an origination number.

Stage 2

  • I used CloudFormation (again, our old friend) to create an IAM role that email_reminder_lambda uses to interact with other AWS services. Really beats searching through the policies!
  • In the Lambda console, I create a function that uses Python 3.9 rundown and use the LambdaRole created via CloudFormation. There are multiple entries called some variation of LambdaRole, so look for the one with SES/SNS and CloudWatch roles.
  • The function in question needs the email address added, so it goes from




Stage 3

  • Making and configuring the state machine through a CloudFormation stack yet again. It has the ability to invoke the email lambda function to send emails, logging permissions and SNS sending abilities.

  • The State machine will be written in Amazon States Language, which looks like JSON to me.

  • Here is the workflow and my interpretation; The actual workthrough is in the instructions.

Start: The function exists

Timer I’m not sure of yet

ChoiceState is obvious with 4 choices - Email only SMS only, Both, or neither. When one of the message options are chosen, it moves on to pushing the message and ends. NoChoice ends the function.

  • The ARN created in Step 2 is put into EMAIL_LAMBDA_ARN
  • Logging is enabled for all events
  • The State Machine is created and given an ARN.

Stage 4

  • This creates the API gateway and Lambda function to act as the front end for the application.
  • I make yet another function in the Lambda console using Python 3.9 as the runtime that supports the API Gateway, which is created now, alongside the API Gateway, API, and Method.
  • The API has the Regional Endpoint and is deployed in the current region.
  • For more control over the information, I don’t click Configure as proxy resource
  • Enable API Gateway CORS eases restrictions on things calling our APIs with different DNS names.
  • The resource (petcuddleotron) is given the POST method to work with api_lambda.
  • Lambda Proxy Integration is checked.
  • The API is deployed and I get an invoke URL.

Stage 5

  • Creating an S3 bucket to hold the visuals of the webpage that allows public access.
  • Static hosting is placed upon the bucket , and I note how straightforward it is on AWS. I’m given a bucket website endpoint.
  • The files are uploaded to the Objects portion of the bucket. Note that I had to click and drag the files for the webpage to appear; Uploading the entire folder did not work, nor did using the upload dialog.
  • Testing the app with information; I use my receiving email set up in Step 1 (It’s not this);

My dog is very enthusiastic about chicken.

  • In Step Functions, under the petcuddleotron app and Executions, I can see it running!

It did fail; It doesn’t seem to like my email address, despite it being the confirmed one. Every failure involves my email being involved.

When I hit SMS only, it does succeed, but I don’t receive the message until I put the 1 in front of my phone number; I had forgotten.

And now my dog can bother me for attention (If she knew how to use technology);



Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

 If you're seeing this post, I'm helping you, and you probably have LI presence: React and share this post to help me in return.   In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory