Last week I composed an article with a sample project on how to manage one time schedules created by Amazon EventBridge Scheduler using StepFunctions.
There I use StepFunctions callback pattern to wait for the schedule to run and then delete the schedule.
In this post I will explain another way to create the schedule and delete it after the given time without the callback pattern, but using a wait state in the execution.
AWS Step functions recently announced SDK support for another 35 services.
This includes the support for EventBridge Scheduler as well. One time schedule is one of the great features supported by EventBridge Scheduler. As the name implies, it allows you to schedule a task just to run once at a given time.
As at now ( February 2023) EventBridge Scheduler doesn’t have native functionality to know if the target task is successful or not.
Intro AWS Step Functions is a Serverless orchestration service that helps to build a workflow with various steps that connect different AWS services. These steps are defined in State Machine, which will be implemented in Amazon States Language (ASL).
There are two types of workflows in Step Functions:
Express flow Standard flow Among many differences, Express flow can only run up to five minutes and Standard flow can run up to one year.
Intro In this project, I will discuss how you can build a simple leave apply/approval system using AWS Serverless services.
These are the main functionalities of this implementation.
Apply for a leave Confirmation for leave application. Send notification to the approver regarding new leave request. Send reminder notification to the approver. Send notification upon approval/rejection. And below services/functionalities are in use in this project:
Step functions SDK integrations for SES, DynamoDB Step functions Parallel processing Step functions wait for callback pattern Lambda function URLs DynamoDB streams with filtering AWS CDK with TypeScript as IAC Architecture State Machine How it works Create a leave request CreateLeave Lambda function accepts leave requester’s email, leave approver’s email, leave dates and reason and is responsible to validate and save it to the DyanmoDB table.
Webhooks are still a preferred choice of many organizations to communicate with 3rd party services. Since webhook calls are event-driven, building a webhook management system with Serverless is a great choice. In this post, I am going to discuss how to build such a webhook management system with AWS Serverless.
In an Application Tracking Systems (ATS), whenever a candidate related event occurs (ex: candidate created, applied for a job, candidate state changed, etc), it might need to call to a registered webhook.
Intro This is how I built a photo booth application with AWS Serverless services.
Once user capture an image and provide an email, background of the image is removed and new background applied and watermark with timestamp will be added. Then the image will be emailed to the given email address.
Below tools and technologies are used to built this.
AWS Lambda with runtime Node.js Step Function S3 SES remove.
NOTE: This post is originally published at dev.to
Intro Recently, there was a hackathon at my work place, Wonderkind, and with one of my colleagues, I created a intelligent door bell with AWS Serverless services + a raspberry pi.
Whenever someone clicks on the button of the ‘door bell’, it will capture a image and check through a Amazon Rekognition faces collection to see if the faces on the image are already indexed.