Sending email via AWS SES within AWS Lambda function

Question

I have created a very basic simple function on AWS Lambda which will be used to accept form submissions.

Part of the function will be to send an email to a particular person, pretty simple. I am trying to use AWS SES in order to do this. I have setup the SES service etc, and verified the account I wish to send to and have been able to send out a test email. All works!!

Now when I try and do the same within AWS Lambda and use the aws sdk it doesn't send out the email. I don't get an error or anything.

Below is the code that I am using for the AWS Lambda function.

Has anyone had any experience using lambda and sending emails via ses, through a lambda function? Or even just using the node.js aws sdk would more than likely be helpful.

var aws = require('aws-sdk');
var ses = new aws.SES({
   accessKeyId: 'myAccessKey',
   secretAccesskey: 'mySecretKey',
   region: 'eu-west-1' 
});

exports.handler = function(event, context) {
    console.log("Incoming: ", event);
    var output = querystring.parse(event);

    var eParams = {
        Destination: {
            ToAddresses: ["[email protected]"]
        },
        Message: {
            Body: {
                Text: {
                    Data: output.Key1
                }
            },
            Subject: {
                Data: "Ses Test Email"
            }
        },
        Source: "[email protected]"
    };

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

AccessKey is not required. Recommended approach is to use IAM Roles to manage access. — swogger
– swogger, Commented Aug 31, 2016 at 14:11
Yes I second @swogger, always should use roles where ever possible which reduces the risk of secret keys getting exposed any since being a plain text javascript on console, is more risky than a packaged lambda code. — Kartik Narayana Maringanti
– Kartik Narayana Maringanti, Commented Dec 4, 2017 at 13:34

Rob Schmuecker · Accepted Answer · 2020-06-09 20:12:12Z

29

It would appear that I had the context.succeed(event) placed in the wrong area of code.

Once I moved it into the sendEmail callback all worked.

var aws = require('aws-sdk');
var ses = new aws.SES({
  accessKeyId: 'myAccessKey',
  secretAccesskey: 'mySecretKey',
  region: 'eu-west-1' 
});

exports.handler = function(event, context) {
  console.log("Incoming: ", event);
  var output = querystring.parse(event);

  var eParams = {
    Destination: {
        ToAddresses: ["[email protected]"]
    },
    Message: {
        Body: {
            Text: {
                Data: output.Key1
            }
        },
        Subject: {
            Data: "Ses Test Email"
        }
    },
    Source: "[email protected]"
};

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

edited Jun 9, 2020 at 20:12

Rob Schmuecker

8,9642 gold badges21 silver badges34 bronze badges

answered Sep 16, 2015 at 13:35

Darren

7951 gold badge6 silver badges11 bronze badges

Sign up to request clarification or add additional context in comments.

9 Comments

Jasper Over a year ago

Darren> Have you tried Java equivalent of the above?

Darren Over a year ago

@Jasper unfortunately I haven't. Have you experienced the same issue?

Jasper Over a year ago

Invoking this works... via rest endpoints from a program running on my computer..... but if i try from some other domain (server) - i see 403 (could be due to cross-domain CORS thing).

Darren Over a year ago

@Jasper - I would need to know a little more about what you are trying to do. Have you asked a question on stackoverflow. If you include the detail of what you are trying to do and how you are achieving it in a question I can have a look at it.

Jasper Over a year ago

I tried invoking this via a simple HTML HTTP Post: <form action="http:///awsfunc" method="POST" > <input type="textarea" width="200" height="100" value="Some Message"> <input type="submit" value="Send"> </form> But console.log incoming is always empty! Although i can invoke this via a Java code successfully!

|

Peters Kings Monday · Accepted Answer · 2022-01-27 11:17:18Z

1

var aws = require("aws-sdk");
var ses = new aws.SES({ region: "us-west-2" });
exports.handler = async function (event) {
  var params = {
    Destination: {
      ToAddresses: ["RecipientEmailAddress", ...],
    },
    Message: {
      Body: {
        Text: { Data: "Test" },
      },

      Subject: { Data: "Test Email" },
    },
    Source: "SourceEmailAddress",
  };

  return ses.sendEmail(params).promise()
};

answered Jan 27, 2022 at 11:17

Peters Kings Monday

573 bronze badges

Comments

halt00 · Accepted Answer · 2017-07-25 01:47:36Z

0

This is because Lambda freezes the container when the function exits and any async processes are frozen, such as your email. This is especially true with Node. See Lambda Programming Model. http://docs.aws.amazon.com/lambda/latest/dg/lambda-introduction.html

answered Jul 25, 2017 at 1:47

halt00

3361 gold badge3 silver badges16 bronze badges

Comments

Julian Corrêa · Accepted Answer · 2021-01-13 12:06:07Z

0

My case is: when you set VPC, the issue happens cause of internet limitation access.

If you remove VPC, everything works fine.

It seems a AWS bug for me.

I opened today a AWS Support for it.

No anwers yet.

answered Jan 13, 2021 at 12:06

Julian Corrêa

64812 silver badges25 bronze badges

Collectives™ on Stack Overflow

Sending email via AWS SES within AWS Lambda function

4 Answers 4

9 Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

9 Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related