Verify we can use main SES in main account for emails

[bofstein]

Ashley to help with how we do the test, can reach out to IAS if needed
Need to figure out an appropriate email package to use to test, maybe email alias addition

[briri]

We are waiting on some info from IAS to finish the test.

I added some logic to the backend emailService to use the AWS SES client directly. Once we get the info from them I will be able to test this out.

[briri]

Sent IAS the config info we need in this ticket.

Once we've got the appropriate info we may need to do something like this python example to generate credentials that will allow us to access the main account.

Here is the complete list of config options.

We may also need to use this AWS.endpoint class to configure it so that we are sending calls on either port 465 or 587.

[briri]

I've added some SSM params to store the SES info:

• /uc3/dev/SesEndpoint the endpoint for the SES instance in the main account
• /uc3/dev/SesBouncedEmailBucket the S3 bucket where any bounce notifications get sent
• /uc3/dmp/tool/dev/DoNotReplyEmail the address we will use as the "sender"
• /uc3/dmp/tool/dev/HelpdeskEmail the helpdesk email that appears in the UI as well as in email signatures

We will want to build a script that processes permanent bounces (e.g. address does not exist or someone flagging us as spam) and handle them appropriately:

• address doesn't exist, should notify the user who added it (unless it was used during signup) and remove it
• address doesn't exist (created during a sign up), deactivate the account and add the email to a blacklist
• flagged as spam, set all of the user's notification preferences to false so we stop emailing them. Display a message in the UI letting them know this has happened.