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

Support SES v2 PutEmailIdentityConfigurationSetAttributes #19363

Closed
jjshoe opened this issue May 13, 2021 · 3 comments · Fixed by #27260
Closed

Support SES v2 PutEmailIdentityConfigurationSetAttributes #19363

jjshoe opened this issue May 13, 2021 · 3 comments · Fixed by #27260
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/ses Issues and PRs that pertain to the ses service.
Milestone

Comments

@jjshoe
Copy link

jjshoe commented May 13, 2021

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • 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
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

v2 of the API allows you to associate a configuration set to a domain, or email. This means you don't have to pass in a configuration set everywhere you call the API or add headers to the email body to get it to use a configuration set.

You can NOT do this via the web ui. You CAN do this via the cli:
aws sesv2 create-email-identity --email-identity ADDRESS-OR-DOMAIN --configuration-set-name CONFIG-SET ; aws sesv2 put-email-identity-configuration-set-attributes --email-identity ADDRESS-OR-DOMAIN --configuration-set-name CONFIG-SET

Source: https://docs.aws.amazon.com/ses/latest/DeveloperGuide/managing-configuration-sets-default.html

New or Affected Resource(s)

  • aws_ses_domain_identity
  • aws_ses_email_identity

References

https://docs.aws.amazon.com/ses/latest/DeveloperGuide/managing-configuration-sets-default.html

@jjshoe jjshoe added the enhancement Requests to existing resources that expand the functionality or scope. label May 13, 2021
@ghost ghost added the service/ses Issues and PRs that pertain to the ses service. label May 13, 2021
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label May 13, 2021
@bill-rich bill-rich removed the needs-triage Waiting for first response or review from a maintainer. label May 14, 2021
@gmx-git
Copy link

gmx-git commented Sep 22, 2022

I guess this also depends on the use of SESv2 AWS SDK. I see there's a plan and a pull request for that.
Maybe we'll need to vote them up (👍) so they can pick up some traction.
Here are the links:
https://github.com/hashicorp/terraform-provider-aws/issues/26796
https://github.com/hashicorp/terraform-provider-aws/pull/26846

Hope this helps move this one forward as well!

@github-actions
Copy link

This functionality has been released in v4.37.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
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/ses Issues and PRs that pertain to the ses service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants