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

aws_cognito_user_pool add support for SES ConfigurationSet #13154

Closed
mousedownmike opened this issue May 4, 2020 · 4 comments · Fixed by #14935
Closed

aws_cognito_user_pool add support for SES ConfigurationSet #13154

mousedownmike opened this issue May 4, 2020 · 4 comments · Fixed by #14935
Assignees
Labels
enhancement Requests to existing resources that expand the functionality or scope.
Milestone

Comments

@mousedownmike
Copy link
Contributor

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

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

resource aws_ses_email_identity example {
  email = "cognito@example.com"
}
resource aws_ses_configuration_set cognito_config {
  name = "cognito-config"
}
resource aws_cognito_user_pool example {
  name = "example-user-pool"
  email_configuration {
    source_arn = aws_ses_email_identity.example.arn
    from_email_address = "Example <${aws_ses_email_identity.example.email}>"
    email_sending_account = "DEVELOPER"
    configuration_set = aws_ses_configuration_set.cognito_config.name
  }
}

References

@mousedownmike mousedownmike added the enhancement Requests to existing resources that expand the functionality or scope. label May 4, 2020
@ghost ghost added the service/cognito label May 4, 2020
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label May 4, 2020
@s16tom
Copy link

s16tom commented Jan 20, 2021

@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!

@mousedownmike
Copy link
Contributor Author

@s16tom I did not have a work around for this, it is one of the few manual steps I perform after creating an environment.

@YakDriver YakDriver self-assigned this Mar 9, 2021
@YakDriver YakDriver removed the needs-triage Waiting for first response or review from a maintainer. label Mar 9, 2021
@github-actions github-actions bot added this to the v3.32.0 milestone Mar 9, 2021
@ghost
Copy link

ghost commented Mar 12, 2021

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!

@ghost
Copy link

ghost commented Apr 8, 2021

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!

@ghost ghost locked as resolved and limited conversation to collaborators Apr 8, 2021
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.
Projects
None yet
3 participants