Forward all emails sent to AWS subdomain to one single account - amazon-web-services

I have many email addresses, one for each user, on a subdomain like so: username#upload.mywebsite.com
I'd like to receive all of these emails into one Inbox for me to use, e.g. combineduploads#mywebsite.com
I'm using AWS Workmail and Route 53. I'm not sure where to start. Maybe this can be done with DNS records?

This can be done using AWS SES and AWS Lambda where you can setup a SES rule to trigger a Lambda function to forward the mails received to a predefined email address.
For more details refer Forwarding Emails to your Inbox Using Amazon SES. You can launch the CloudFormation stack to automate the majority of the configurations.

Related

how to receive emails using the aws ses and aws sns?

I am trying to receive emails on a domain email like xyz#example.com and I have done the following steps to get the results but am unable to get that.
Firstly, I have created an SNS topic and linked that SNS topic with HTTPS protocol to a rest API to receive the incoming email details. And then in SES firstly I have verified the domain and then in the email receiving section I have created a rule set and activated that rule set and I have not added recipient condition and in the action I am using AWS SNS topic and same topic which I have created for this email receiving. But I am not able to receive the email content to the endpoint which I have linked to SNS topic. I have added the MX record in Cloudflare DNS and I am using us-east1 for value endpoint.
How can I implement this?
Check your destination rules, if you need receive all traffic domain add your naked domain: example.com, if you need receive traffic for specific address: user#example.com, also check if You have more than one MX record, if You have two or more setup priority for SES.

Start Server through email in AWS

I have requirement where authorized people will send an email and then an EC2 server should start.
We have decided to use SES and Lambda for this.
I have learned that we can set up rule in SES which then can trigger a Lambda function where we will have boto3 code to start the EC2 instance.
I was going through Amazon SES Email-Receiving Concepts to do a Proof of Concept for this.
I have some questions:
To do POC in my AWS account do I need my own Domain name?
In real time when we set these rule where the authorized person will send email to which email-address address? And any particular format for it?
You would need a domain name (or sub-domain) with an MX record pointing to Amazon SES, or your existing email system could forward the email to the SES endpoint.
You could then configure SES to trigger a Lambda function for each incoming email. You could then code the Lambda function to turn on the EC2 instance. It could even look at who sent the email and make a decision about which EC2 instance to start. This would all be your own code, so the contents of the email is totally up to you!
For details, see: New – Receive and Process Incoming Email with Amazon SES | AWS News Blog
Let us know how it worked for you!

Hosting Google Domain on AWS EC2

I'm not sure if this is the place to ask this.
I recently bought a domain from Google and setup email forwarding so that emails sent to 'me#domain.com' get sent to the gmail of the account that owns the domain, then I stared an ec2 instance on AWS. I changed my nameservers in Google domains so that when I go to my domain, I get my ec2 instance and this works correctly.
However, now my email forwarding no longer works, so I tried setting up a MX in route 53 on AWS using
5 gmr-smtp-in.l.google.com.
10 alt1.gmr-smtp-in.l.google.com.
20 alt2.gmr-smtp-in.l.google.com.
30 alt3.gmr-smtp-in.l.google.com.
40 alt4.gmr-smtp-in.l.google.com.
with no name as I have read online. I am still not recieving emails like i used to and am unsure what to do. Thanks in advance
Have you considered using AWS SES and AWS Lambda to forward your emails?
First, you need to verify your domain - Amazon SES Domain Verification TXT Records
Second, create an S3 bucket with a unique and meaningful name. This will be used to store emails, for example ascisolutions.com-emails . Create a folder inside this bucket to store emails.
Third, create a Lambda function to forward the emails. See AWS Lambda SES Email Forwarder for files needed for AWS Lambda and instructions how to set it up as it requires to modify a config file.
Next, you need to create a rule set - Creating a Receipt Rule Set for Amazon SES Email Receiving
After that, you need to create a rule in the new rule set to let SES know what to do with the email that it received - Creating Receipt Rules for Amazon SES Email Receiving
Next, you want to update your MX records - Publishing an MX Record for Amazon SES Email Receiving
When you're done, wait a few minutes for DNS to update and then test to see if email forwarding is working.
Hope this was helpful.

AWS: how to manage email

I have domain on Godaddy. I will migrate dns for this domain from godaddy to AWS. However, AWS seems to be not the best service to use email (send and receive message like in gmail).
I'm going to use 2 emails: support#example.com and contact#example.com. one of them I will use to send notifications from app on AWS. Second one, I want to use like typical email for daily personal duties.
What solution you can recommend me?
Set me record on AWS route 53 after migration to some another service?
You could use AWS Simple Email Service (SES) to send notifications programmatically from applications using AWS SDK.
Receiving email with SES is also supported, and you can use it to trigger other AWS services, such as Lambda or SNS. In addition, SES can forward received messages to Amazon WorkMail which is an email client you were looking for.
In case if you dont want to pay to Amazon WorkMail since it will cost little more , you can use aws s3 to receive your daily mails.
https://aws.amazon.com/blogs/ses/receiving-email-with-amazon-ses/

AWS SES mail account setup

I am trying to create an application in which I forward an email to AWS SES, have a lambda function parse that email, extract the required information, and store it in a database. I don't want to store in S3.
I registered for a Route53 domain and received a domain name (example.com). I want to forward emails from my gmail address to an alias in my domain (test#example.com). I created a rule-set in SES, and verified my domain (example.com).
I can't figure out how to create email accounts in my domain (example.com). I would like to create something like test#example.com, where I could forward emails from my personal gmail account. Anyone know how I would do this?
Go through the steps in the documentation here. By default all emails for any address in the domain will be sent to your Lambda function when you create the receipt rule. You will have to specify an address (test#domain.com) in the first step of creating a receipt rule to only send emails for that address to the Lambda function.