-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
Support for SES Email feedback forwarding configuration #14622
Comments
Duplicate of #4182 |
Vote for option 2 - Create a dedicated resource called As with the existing resource
|
I'm facing this issue now. Suggestion by @djravine really make sense for me. |
I opened the draft pull request for this issue. |
What's the status on this new resource? I need to disable feedback forwarding. |
+1. Importing our SES into Terraform, but this specific setting does not seem to be available anywhere in the TF provider? From the AWS console UI, it looks like this would belong to |
This functionality has been released in v4.38.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Description
There is a configuration about Email feedback forwarding for SES. Currently it is not supported in any of the SES resources. people have to manually do it from the aws console.
There is a challenge to decide how we can support this configuration in TF. I can think of two options:
aws_ses_domain_identity
andaws_ses_email_identity
. Adding a parameter to identity resource itself for notification configuration will be confusing to the users.aws_ses_identity_feedback_forwarding_enabled
. Having a dedicated resource for a simple configuration might be an overkill.Given both solutions are not perfect I would vote for 2 as it will not touch any existing resources.
I wanted to get some feedbacks on this. Thanks!
The text was updated successfully, but these errors were encountered: