Conversation
doshitan
left a comment
There was a problem hiding this comment.
I don't think we need to pass the configuration set around do we? It should be set as the default for the sender already in infra/modules/notifications-email-domain/resources/main.tf.
We'll need to update various docs and comments (anywhere mentioning "Pinpoint"). But that could just be on the template PR.
b068edc to
e510ab2
Compare
doshitan
left a comment
There was a problem hiding this comment.
Looks to be working well via https://p-231-app-dev-1629703657.us-east-1.elb.amazonaws.com/email-notifications, which looks to be using the new config.
Can probably open up the template PR at this point.
It's set as default on line 15 of infra/modules/notifications-email-domain/resources/main.tf |
- Replace pinpoint_app_id output with ses_configuration_set and ses_from_email - Updates outputs for all app templates (app, app-flask, app-nextjs, app-rails) - Completes migration from Amazon Pinpoint to direct SES usage Related to Amazon Pinpoint end of support (October 30, 2026) See: https://docs.aws.amazon.com/pinpoint/latest/userguide/migrate.html 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
63e091b to
e1700c3
Compare
Ticket
Resolves #{TICKET NUMBER OR URL}
Changes
Context for reviewers
Testing
Preview environment for app-nextjs
Preview environment for app-flask
♻️ Environment destroyed ♻️
Preview environment for app
♻️ Environment destroyed ♻️
Preview environment for app-rails
♻️ Environment destroyed ♻️