Enable feedback notifications for SES in all spaces

[exalate-issue-sync]

"enable_feedback_notifications": "true"

https://docs.cloud.gov/platform/services/aws-ses/#reputation-protection

QA Notes

null

DEV Notes

null

Design

null

See full ticket and images here: FECFILE-3404

Pull Request: https://services.cloud.gov/#aws-ses

[exalate-issue-sync]

Dan Fowlkes commented: This setting is a “Flag to toggle creation of SNS topics for feedback notifications.”

SNS is Amazon [Simple Notification Service|https://docs.aws.amazon.com/sns/latest/dg/welcome.html]. I assume that [cloud.gov|http://cloud.gov] supports it. Do we (or FEC) already use it for other notifications?

More:

[https://docs.aws.amazon.com/ses/latest/dg/configure-sns-notifications.html|https://docs.aws.amazon.com/ses/latest/dg/configure-sns-notifications.html|smart-link]

[https://docs.aws.amazon.com/ses/latest/dg/receiving-email-action-sns.html|https://docs.aws.amazon.com/ses/latest/dg/receiving-email-action-sns.html|smart-link]

[exalate-issue-sync]

Todd Lees commented: [~accountid:712020:3a738b19-6415-43b4-81c1-e92f1f7586f3] I don’t believe we need to get into the nitty gritty of sns for this. I think it’s part of the binding setup if we say we want it on, they ask us for what email to send it to

{quote}To be notified of complaints, bounces, or successful delivery of emails sent from your identity, set {{"enable_feedback_notifications": "true"}} when creating your SES service instance and provide a webhook when binding. See [Cloud.gov Services Reference: AWS Simple Email Service|https://services.cloud.gov/#aws-ses] for full details.{quote}

->

[https://services.cloud.gov/#aws-ses|https://services.cloud.gov/#aws-ses|smart-link]

{quote}Binding

Request Parameters

…

notification_email string - Email to subscribe to feedback notifications.{quote}

[exalate-issue-sync]

Dan Fowlkes commented: Testing first in DEV:

{noformat}danguyf@fecbuntu:~/repos $ cf unbind-service fecfile-web-api fecfile-api-ses
Unbinding app fecfile-web-api from service fecfile-api-ses in org fec-fecfile / space dev as dfowlkes@precision-solutions.com...
Deleting service binding xxx-xxx-xxx-xxx-xxx...
OK

danguyf@fecbuntu:~/repos $ cf delete-service fecfile-api-ses
This action impacts all resources scoped to this service instance, including service bindings, service keys and route bindings.
This will remove the service instance from any spaces where it has been shared.
Really delete the service instance fecfile-api-ses? [yN]: y
Deleting service instance fecfile-api-ses in org fec-fecfile / space dev as dfowlkes@precision-solutions.com...

Delete in progress. Use 'cf services' or 'cf service fecfile-api-ses' to check operation status.
OK

danguyf@fecbuntu:~/repos $ cf create-service aws-ses domain fecfile-api-ses -c '{"admin_email":"lbeaufort@fec.gov", "domain":"dev-ses.fecfile.fec.gov", "enable_feedback_notifications":true}'
Creating service instance fecfile-api-ses in org fec-fecfile / space dev as dfowlkes@precision-solutions.com...

Create in progress. Use 'cf services' or 'cf service fecfile-api-ses' to check operation status.
OK

danguyf@fecbuntu:~/repos $ cf bind-service fecfile-web-api fecfile-api-ses -c '{"notification_email":"dfowlkes@precision-solutions.com"}'
Binding service instance fecfile-api-ses to app fecfile-web-api in org fec-fecfile / space dev as dfowlkes@precision-solutions.com...
OK

TIP: Use 'cf restage fecfile-web-api' to ensure your env variable changes take effect
danguyf@fecbuntu:~/repos $ {noformat}

Confirmed that the DNS records did not change. (phew!)

The following environment variables are now set:

• {{bounce_topic_arn}}
• {{complaint_topic_arn}}
• {{delivery_topic_arn}}

After re-binding, the AWS secret and key reset. I gave it my email address and received:

!image-20260910-193452.png|width=845,alt="image-20260910-193452.png"!

[exalate-issue-sync]

Dan Fowlkes commented: Enabled feedback notifications in STAGE, TEST, and PROD.

On binding I set {{notification_email}} to Laura’s address in those environments.

[exalate-issue-sync]

Dan Fowlkes commented: [~accountid:5b92c509d0b4022bdc51bdf4] - I had not bothered to click the confirmation link in the notifications so mine too had timed out. As a test I unbound and then rebound the SES service in DEV with my address and then confirmed the subscriptions successfully.