Skip to content
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

Consider upgrading to aws_sesv2_email_identity #109

Open
jsf9k opened this issue Oct 2, 2024 · 0 comments
Open

Consider upgrading to aws_sesv2_email_identity #109

jsf9k opened this issue Oct 2, 2024 · 0 comments
Labels
improvement This issue or pull request will add or improve functionality, maintainability, or ease of use terraform Pull requests that update Terraform code

Comments

@jsf9k
Copy link
Member

jsf9k commented Oct 2, 2024

💡 Summary

Consider using the aws_sesv2_email_identity resource instead of the aws_ses_domain_identity resource, although it would likely be a destructive upgrade.

Motivation and context

The v2 API is the way forward, and new SES features will only be supported in the v2 API.

Implementation notes

See here.

@jsf9k jsf9k added improvement This issue or pull request will add or improve functionality, maintainability, or ease of use terraform Pull requests that update Terraform code labels Oct 2, 2024
jsf9k added a commit that referenced this issue Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement This issue or pull request will add or improve functionality, maintainability, or ease of use terraform Pull requests that update Terraform code
Projects
None yet
Development

No branches or pull requests

1 participant