Closed nexavolve-colin closed 1 month ago
Voting for Prioritization
Volunteering to Work on This Issue
[!WARNING] This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.
Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.
This functionality has been released in v5.60.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. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Description
AWS have released EventBridge as a destination for publishing SES sending events. Need to update the aws_sesv2_configuration_set_event_destination resource to reflect this.
Affected Resource(s) and/or Data Source(s)
aws_sesv2_configuration_set_event_destination
Potential Terraform Configuration
References
https://aws.amazon.com/about-aws/whats-new/2024/06/amazon-ses-publishes-email-sending-events-eventbridge/ https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/sesv2_configuration_set_event_destination https://docs.aws.amazon.com/ses/latest/dg/monitoring-eventbridge.html
Would you like to implement a fix?
None