daltonfury42

Posted on Sep 12, 2020 • Edited on May 23, 2021

AWS SES + Gmail = Free Business Email ID

#startup #aws #productivity

My website is hosted on AWS Free Tier, and I wanted to create a free company/business email address for people to contact me. If you are already on AWS, and want to create an email address like contact@simplq.me it doesn't cost anything.

What you need:
1) An AWS Account
2) A domain name (simplq.me in my case)
3) Gmail account (Other email services should also work)

What you don't need: A GSuite Account

(If your domain is on Google Domains, setting up email forwarding is easy.)

I've covered all the necessary steps in brief, but if you need help or get stuck somewhere, let me know in the comments.

If you want two way communication, not all regions support it. I set this up in us-west-2 (Oregon) even though my website is hosted in ap-southeast-1 (Singapore).

Setup SES - Simple Email Service

On AWS Console, switch to us-west-2, go to SES, and verify your domain:

If your DNS is managed by Route53, Amazon can automatically update the entries, click on "Use Route53" button on the next page. Otherwise, you have to manually set the entries in your current DNS registrar.

Verify Your Current Email

This step is easy, your current Gmail address that you want Amazon to relay all communications to, verify it with SES.

You'll get a confirmation email, as part of the verification process.

Configure SES Email Forwarder

In the coming steps, we will configure SES to trigger a lambda which will forward emails to our personal email.

Create a blank Node.js 12.x runtime Lambda function with no triggers in the same region, and use this file as the function code.

There is a config object in the code which requires some tweaking:



var defaultConfig = {
  fromEmail: "contact@simplq.me",
  subjectPrefix: "",
  emailBucket: "<s3-bucket-name>",
  emailKeyPrefix: "mails/",
  allowPlusSign: true,
  forwardMapping: {
    "contact@simplq.me": [
      "<your-gmail-id>@gmail.com"
    ]
  }
};

fromEmail should be the business email which your customers would see. We will later create an S3 bucket to store our emails. Choose a bucket name and give it as emailBucket. In the forwardMapping section, you should configure the gmail address which you verified in the previous step.

arithmetric/aws-lambda-ses-forwarder is a awesome repo, it supports many more configurations, you should check it out if you want to create and forward multiple emails, or forward emails to multiple people.

Attach this policy to the service role of the Lambda, to give it access to the S3 bucket, and also SES:



{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "s3:PutObject",
                "s3:GetObject"
            ],
            "Resource": "arn:aws:s3:::<s3-bucket-name>/*"
        },
        {
            "Sid": "VisualEditor1",
            "Effect": "Allow",
            "Action": "ses:SendRawEmail",
            "Resource": "*"
        }
    ]
}

Create a Rule in SES

This ties everything together, go back to SES console and create a new Email Receiving -> Rule Set. You will set a rule, where you configure two "Actions", one to save all emails to a S3 bucket which you can create from this screen, and another to trigger the Lambda created in the previous setup to forward the mails. Use the below screenshot as reference:

At this point, if you send an email to your business email, the personal Email ID should receive it. Test and make sure that it works, use Cloudwatch Logs for the lambda to debug in case of issues.

Configure Gmail

Next is to add this new email as a new identity to your Gmail account. Go to SES's SMTP Settings and create a new SMTP Credential.

At the end, you'll get a username and a password, which you should add to your Gmail Settings:

Last Step - Verification

Initially your newly configured Amazon SES service will be quarantined (sandboxed) by Amazon as a measure of protection against possible abuse and spam. To remove it from quarantine and allow normal mailing, as the last step, you need to open a support ticket to Amazon and fullfill a request. Otherwise you will see how the emails you send bounce with the following error message:



554 Message rejected: Email address is not verified. The following identities failed the check in region ...

They approved within minutes in my case. Go to Sending Statistics section to raise a request:

That's it! Your business email is ready to use. Let me know in the comments section if you face any issues. Hope you enjoyed it.

If you want to reach out to me for consulting or mentoring, you can book a slot here.

Top comments (31)

Sebastian Weigand • Sep 14 '20

Pro-tip: You can do all of this with built-in functionality with Google Domains, where you can establish mail aliases and forwarding rules from your custom domain. There's no need for extra complication or additional services.

See this article for more information.

Anurag Singh • Sep 24 '20 • Edited

Thanks for this info, i was using improvmx till now even though I have a google domain.

daltonfury42 • Sep 14 '20

Yep, if your are willing to transfer your domain to Google Domains, this is looking very easy!

wandetri • Nov 2 '20 • Edited

Hi Thanks for this trick
Its Working!
but there is a problem, all of my sent email goes to Promotion tab in gMail Inbox

edit
After I modify the email content to longer and more 'personal' instead of 'Test Email', it goes to my main inbox.

Thanks!

Jörg Rech • Apr 1 '22

Hi! Just implemented it for one of my domains and it works really well - thank you! One question though: Do I need to "register" every name of a domain at Gmail or should it work out of the box? For example:

I have the following config in the Lambda code:

  forwardMapping: {
    "@<MY_DOMAIN>.com": [
      "<ME>@gmail.com"
    ]
  }

However, only @.com is forwarded to Gmail (where I added this email address) but emails to info@.com is only stored in S3 but not forwarded.

Chris Hayes • Jul 22

For what it's worth - I haven't had that issue, it works as wildcard for me with all the email addresses I don't specifically mention.

Meir Gabay • Sep 13 '20

An honest question - is this better than using Google's MX records in Route53? I'm trying to understand the benefits of this method

Ref - support.google.com/a/answer/614969...

daltonfury42 • Sep 13 '20 • Edited

I've not gotten chance to play with GSuite / GApps for business much, but I am guessing this works only when you have a paid GSuite Account?

This solution is when you have a free personal Google account. Please correct me if I am wrong, though.

Meir Gabay • Sep 13 '20 • Edited

I think you are right, my assumption was that you have a GSuite account since you talked about a "company/business email address". I don't think it's possible to use MX records with a personal account, thanks for the clarification

daltonfury42 • Sep 14 '20

Hey. Thanks for pointing this out.. I'll edit the post to make this clear.

Shreyash Gupta • May 18 '21

Hi,

I am the Co-founder of Looseleaf which is a startup in the education sector of India. We currently want to get our domain emails using the AWS SES. I would like to ask if you would be interested in helping us out as it seems that you know what you are doing. Let's discuss further details below!
Contact Email: officiallooseleaf@gmail.com
Our website: looseleaf.in

daltonfury42 • May 21 '21

Hi Shreyash,

I'd be happy to help. Let's connect this weekend.

Shreyash Gupta • May 21 '21

Just send me an email with your times that you can hop on a google meets call this weekend and then we will go on from there!

andrewrooke • Sep 17 '20

While this may be a good way to get started quickly, have you thought through the implications for SPF and DMARC ?

Every time i create a business domain and email service, I ensure I configure SPF and DMARC (and ideally DKIM) to secure my email service.

Aftab Naveed • Dec 26 '23

I just tried configuring it on my GMAIL account, I was able to make the AWS SES part working and can see emails arriving to my S3 bucket, however when I try to connect my Gmails' "Send mail as " I get this error

Authentication failed. Please check your username/password.
Server returned error: "DNS Error: DNS type 'aaaa' lookup of smtp.email-smtp.us-east-1.amazonaws.com responded with code NXDOMAIN DNS type 'a' lookup of smtp.email-smtp.us-east-1.amazonaws.com responded with code NXDOMAIN, code: 553"

Lewis Cowles • Sep 14 '20

I sort of love you for this, but you can setup any email host just using route53 and likely own less of a footprint, and escape gmail

daltonfury42 • Sep 15 '20

Hey. I want to give this a try, can you give me a rough idea. Can I do this using my personal gmail account? Otherwise which mailbox providers allow this?

Lewis Cowles • Sep 15 '20

Sure, so I don't know how much you understand DNS, but the way I use a shared host to do this is to tell them I'm hosting a domain with them. I don't change the nameservers, because I love AWS and am cheap.

I can then go into their DNS settings, take out the MX records and place them into my AWS.

You can use AWS UI to do this, or Terraform, or any other IaC tooling that integrates with your cloud provider (doesn't have to be AWS, can be Azure, GCP or DigitalOcean AFAIK)

There are some gotchas. I don't think Heroku supports, but you can have heroku only own a CNAME.
Also you should not move other subdomains like webmail to your domain. Let the shared host do that with SSL and all the bells and whistles to secure your email from attackers. You can also front that with SES and forwarding rules, although I was gutted to see that.