Use AWS SES to send email about kitsune HOT 10 CLOSED

FTR we're currently using SocketLabs. Let's make sure that we ping WebOps when this is done that we don't need the SocketLabs acc anymore

from kitsune.

AWS verified the domain 🥂

I'll proceed with adding email address and with testing on Monday and plan on switching SCL3 to SES within next week.

from kitsune.

@glogiotatidis is there anything you need me to automate here?

I understand that we need to verify the address and then we can use SES. I don't see anything to automate. Do I miss something?

from kitsune.

We are going to validate the domain in SES which will unlock all email address for sending.

Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1432747

from kitsune.

1. Created IAM user for scl3
2. Pushed and Verified working on SCL3 staging
3. Pushed and Verified working on SCL3 production
4. Created IAM user for AWS dev (sumo-dev-ses-smtp)
5. Created issue to track deletion of IAM user created in (1) after SCL3 decom. mozmeao/infra#716

Credentials are in sumo-encrypted

from kitsune.

Also created

• sumo-stage-ses-smtp-user
• sumo-prod-ses-smtp-user

for AWS stage and prod

from kitsune.

Note: if for some reason we end up sticking with SocketLabs, AWS automatically throttles port 25 outbound traffic. We had a similar issue in MDN, changing the SocketLabs port allowed us to bypass the throttle.

from kitsune.

We need to verify [email protected] email on SES. I filed bug 1428741 to identify the users receiving those emails and then proceed with the verification.

from kitsune.

We need to verify [email protected] email on SES. I filed bug 1428741 to identify the users receiving those emails and then proceed with the verification.

No MX record for support.m.o thus nobody gets those emails and we can't verify Email in AWS. Ops will create an MX record and point emails to a private Google Group so we can verify. Progress in bug 1428741

from kitsune.

@glogiotatidis is there anything you need me to automate here?

from kitsune.