-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
aws_cognito_user_pool add support for SES ConfigurationSet #13154
Comments
@mousedownmike did you work around this at all? This is more of a pain than other similar issues I've encountered, as the AWS CLI does not let you just update this field - you have to provide all Cognito User Pool config otherwise it gets replaced by defaults. I'm currently using a provisioner on the user pool that is using the AWS CLI to invoke a lambda function, then reading, updating and then rewriting the Cognito config in that. It's a horrendous work around though, so any other pointers would be appreciated! |
@s16tom I did not have a work around for this, it is one of the few manual steps I perform after creating an environment. |
This has been released in version 3.32.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 for triage. Thanks! |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Description
The AWS CreateUserPool and UpdateUserPool APIs now support a ConfigurationSet EmailConfiguration option. It would be great to incorporate this into the existing
aws_cognito_user_pool
resource.New or Affected Resource(s)
aws_cognito_user_pool
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: