[AWS SDK for Go Migration] SES (Simple Email) Service

[breathingdust]

Description

To align with the dates described on #32976 the SES (Simple Email) Service requires migration to rely fully on AWS SDK for Go v2. This change should be mechanical in nature and not introduce any behavior changes.

The maintainer team will be working on these migrations but as always, help from the community is always appreciated. We would require passing acceptance tests for the entire set of resources being migrated. (We will also validate on review)

For further information about the migration, please see the parent issue #32976.

Resources In Scope for Migration

"aws_ses_active_receipt_rule_set"
"aws_ses_configuration_set"
"aws_ses_domain_dkim"
"aws_ses_domain_identity"
"aws_ses_domain_identity_verification"
"aws_ses_domain_mail_from"
"aws_ses_email_identity"
"aws_ses_event_destination"
"aws_ses_identity_notification_topic"
"aws_ses_identity_policy"
"aws_ses_receipt_filter"
"aws_ses_receipt_rule"
"aws_ses_receipt_rule_set"
"aws_ses_template"

Data Sources In Scope for Migration

"aws_ses_active_receipt_rule_set"
"aws_ses_domain_identity"
"aws_ses_email_identity"

References

• [Provider]: Migration to aws-sdk-go-v2 #32976

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[HubbardHarvey3]

@kamilturek I didn't think to self assign this issue, but I am ironing out what I hope are the last few failing acceptance tests.
I would like to finish and post a merge request.
However, since you were first to assign the issue to yourself, I will stop if you would rather complete it.

[kamilturek]

@HubbardHarvey3 Sorry, I had no idea someone is already working on it. Please finish your work. I'll unassign myself.

[HubbardHarvey3]

No worries, I should have posted a comment earlier.
Thank you very much for understanding.

[github-actions]

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.

[github-actions]

This functionality has been released in v5.62.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!

[github-actions]

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.