Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proof of concept derisking for email notifications #319

Closed
5 tasks
Tracked by #375
loganmeetsworld opened this issue Dec 9, 2022 · 0 comments · Fixed by #411
Closed
5 tasks
Tracked by #375

Proof of concept derisking for email notifications #319

loganmeetsworld opened this issue Dec 9, 2022 · 0 comments · Fixed by #411
Assignees
Labels
Milestone

Comments

@loganmeetsworld
Copy link
Contributor

loganmeetsworld commented Dec 9, 2022

Outcome: An end-to-end proof of concept sending a simple email from our application to a test user account. For example, emails the applicant when their domain request is submitted.

This covers the ability for us to send existing registrants and domain applications emails to notify them of actions taken on their applications. We have many use cases for being able to email applicants and domain managers. This ticket doesn't include implementing any of those specific emails, but rather derisking the infrastructure needed for it.

  • Set up access for dev team to CISA AWS account and ensure SES is present (blocked pending access)
  • Setup SES to send emails
  • Find a client that works for connecting to SES through our application
  • Figure out a way to store SMTP credentials so our application has access
  • Related, connect SES to our cloud.gov account through a brokerpak or some other means.

Helpful resources for figuring this out will be the data.gov team that wrote the broker, the Notify team, and other folks that have made this work with cloud.gov.

This will be blocked on our access to AWS accounts.

@loganmeetsworld loganmeetsworld added this to the Sprint 11 milestone Dec 9, 2022
@loganmeetsworld loganmeetsworld changed the title Proof of concept derisking - Email sending Proof of concept derisking for notifications (via email) Dec 9, 2022
@loganmeetsworld loganmeetsworld changed the title Proof of concept derisking for notifications (via email) Proof of concept derisking for email notifications Dec 9, 2022
@calerubensteingsa calerubensteingsa removed this from the Sprint 11 milestone Jan 9, 2023
@calerubensteingsa calerubensteingsa added this to the Sprint 13 milestone Jan 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants