Skip to main content

Lambda Function with Scheduled Events

 Scheduled events are suppose to happen at regular intervals based on a rule set. Scheduled events are used to execute Lambda function after an interval which is defined in cloudwatch services. They are best used for working on cron jobs along with AWS Lambda. This chapter will explain with simple example how to send mail after every 5 minutes using scheduled events and AWS Lambda.

Requisites

The requirements for using Lambda function with Scheduled events are as follows −

  • Verify email id using AWS SES
  • Create Role to use AWS SES, Cloudwatch and AWS Lambda
  • Create Lambda Function to send email
  • Add rule for scheduled events from AWS CloudWatch
Example

The example that we are going to consider will add CloudWatch event to the AWS Lambda function. Cloudwatch will trigger AWS Lambda based on the time pattern attached to it. For Example, in the example below we have used 5 minutes as the trigger. It means for every 5 minutes, AWS Lambda will be triggered and AWS Lambda will send mail whenever triggered.

The basic block diagram for the same is shown below −

Basic Block Diagram
Verify Email ID using AWS SES

Log in to AWS and go to AWS SES service as shown below −

Customer Engagement

Now, click Simple Email Service as shown −

Simple Email

Click Email Addresses on left side as shown −

Email Address

It displays a button Verify a New Email Address. Click it.

Verify Email Address

Enter Email Address you want to verify. Click Verify This Email Address button. You will receive mail from AWS on that email id with email subject: Amazon Web Services – Email Address Verification Request in region US East (N. Virginia)

Click the link given in the mail to verify email address. Once verified, it will display the email id as follows −

Display Email
Create Role to use AWS SES, Cloudwatch and AWS Lambda

You can also create a role which gives permission to use the services. For this, go to IAM and select Role. Add the required policies and create the role. Observe that the role created here is events with lambda.

Event With Lambda
Create Lambda Function to Send Email

You will have to follow the steps to create Lambda function using runtime as nodejs.

Lambda Event Emails

Now, add trigger to Lambda as shown −

Add Triggers Lambda

Add details to CloudWatch Events Trigger as shown below −

Cloudwatch Events

Note that the event will be triggered after every 5 minutes as per the rule trigger created.

The Lambda code for sending an email is given below −

var aws = require('aws-sdk');
var ses = new aws.SES({
region
: 'us-east-1'
});
exports
.handler = function(event, context, callback) {
var eParams = {
Destination: {
ToAddresses: ["xxxxxxxt12@gmail.com"]
},
Message: {
Body: {
Text: {
Data: "this mail comes from aws lambda event scheduling"
}
},
Subject: {
Data: "Event scheduling from aws lambda"
}
},
Source: "coxxxxxx@gmail.com"
};
console
.log('===SENDING EMAIL===');
var email = ses.sendEmail(eParams, function(err, data) {
if (err) console.log(err);
else {
console
.log("===EMAIL SENT===");
console
.log("EMAIL CODE END");
console
.log('EMAIL: ', email);
context
.succeed(event);
callback
(null, "email is send");
}
});
};

Now, we need the AWS SES service. You can add this using the code shown as follows −

var aws = require('aws-sdk');
var ses = new aws.SES({
region: 'us-east-1'
});

To send mail from nodejs, we have created eParams object which has details like the example mail, to mail id and the body with message as follows −

var eParams = {
Destination: {
ToAddresses: ["xxxxxxxx12@gmail.com"]
},
Message: {
Body: {
Text: {
Data: "this mail comes from aws lambda event scheduling"
}
},
Subject: {
Data: "Event scheduling from aws lambda"
}
},
Source: "coxxxxxx@gmail.com"
};

The Lambda code to send email is as follows −

var email = ses.sendEmail(eParams, function(err, data) {
if (err) console.log(err);
else {
console.log("===EMAIL SENT===");
console.log("EMAIL CODE END");
console.log('EMAIL: ', email);
context.succeed(event);
callback(null, "email is send");
}
});

Now, let us save this Lambda function and check the email id for mails. The screenshot shown below shows that the mail is sent from AWS Lambda after every 5 minutes.

Event Scheduling

Comments

Popular posts from this blog

Unix / Linux - Special Variables

W e will discuss in detail about special variable in Unix. In one of our previous chapters, we understood how to be careful when we use certain nonalphanumeric characters in variable names. This is because those characters are used in the names of special Unix variables. These variables are reserved for specific functions. For example, the  $  character represents the process ID number, or PID, of the current shell − $echo $$ The above command writes the PID of the current shell − 29949 The following table shows a number of special variables that you can use in your shell scripts − Command-Line Arguments The command-line arguments $1, $2, $3, ...$9 are positional parameters, with $0 pointing to the actual command, program, shell script, or function and $1, $2, $3, ...$9 as the arguments to the command. Following script uses various special variables related to the command line − #!/bin/sh echo "File Name: $0" echo "First Parameter : $1" echo "Second Parameter :...

FTP Server : Install Pure-FTPd

  Install Pure-FTPd to configure FTP Server. [1]. Install and Configure Pure-FTPd. # install from EPEL [root@www ~]# dnf --enablerepo=epel -y install pure-ftpd [root@www ~]# vi /etc/pure-ftpd/pure-ftpd.conf # line 77: change (no Anonymous) NoAnonymous                  yes # line 451: uncomment (if you use only IPv4) IPV4Only                     yes # line 460: uncomment (if you use only IPv6) IPV6Only                     yes [root@www ~]# systemctl enable --now pure-ftpd [2]. If SELinux is enabled, change boolean setting. [root@www ~]# setsebool -P ftpd_full_access on [3]. If Firewalld is running, allow FTP service ports. [root@www ~]# firewall-cmd --add-service=ftp --permanent success [root@www ~]# firewall-cmd --reload success

LINUX List files and directories using SSH

In order to list all files and directories using an SSH client, you would need to execute the appropriate command. The command name, in this case, is ls and it accepts various parameters. When using the command alone (without arguments): ls the output will be all visible files and folders without additional formatting or information. In order to view more information about the files (such as their permissions, ownership, last modified date, etc) and at the same time to list the files and directories, you would need to supply additional arguments to the command. The most common arguments are as follows: ls –a(Short from –all) Lists all files and folders including hidden (starting with a dot) files and directories. ls –R (Short from –Recursive) Lists recursively (i.e follows subfolders as well) all files and folders under the current directory. ls -l (Short from –long) Lists all files and folders, each on a separate line, and provides additional information about them (permission...