Open mjtravers opened 2 years ago
3/16/22 Refinement Meeting: Laura mentioned that EFO has an existing service, and it may be worth exploring. Dev team will start looking into this one first. (Low confidence) No AWS structure set up. There will be a high level of external security scrutiny on this.
Laura's order of preference, most to least: Use what we have, then SaaS (Fedramped), then AWS
Adjusted ticket to be research-only. @mjtravers will create an implementation ticket to follow.
Cloud.gov article on sending email: https://cloud.gov/knowledge-base/2021-09-21-sending-emails-from-clouddotgov/
Noting here that there's an SMTP broker (that uses AWS SES on the backend) which was developed outside the cloud.gov team. It may be something that comes in-boundary for cloud.gov later, or it may be something you want to run yourself. (For the latter case, you can see how the data.gov team prepares the broker as an app and deploys it.
On hold until we get more details on how the email functionality will integrate with the app. The solution picked will be informed by this integration.
Noting here that there's an SMTP broker (that uses AWS SES on the backend) which was developed outside the cloud.gov team. It may be something that comes in-boundary for cloud.gov later, or it may be something you want to run yourself. (For the latter case, you can see how the data.gov team prepares the broker as an app and deploys it.
@mogul thanks so much for this suggestion!
@mjtravers @lbeaufort is this a spike ticket? Recommend title being re-written to make that clear. What is the definition of done for the ticket? Should we move this back to AA to flesh out?
Research services to figure out to best send out emails from the app.
Acceptance Criteria
QA Notes
null
DEV Notes
null
Design
null
FECFILE-363