AWS Cognito User Pool - Ability to set Remember User Device to Always

[ghost]

This issue was originally opened by @lama-ank as hashicorp/terraform#25841. It was migrated here as a result of the provider split. The original body of the issue is below.

---

Current Terraform Version

Terraform v0.12.29

Use-cases

Setting Remember Device to "Always" in AWS Cognito User Pool

Attempted Solutions

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cognito_user_pool
The cognito_user_pool provider has these options for devices, but not one to always remember the user device.
challenge_required_on_new_device 
device_only_remembered_on_user_prompt 

Proposal

Adding an argument to set the remember user device option of Cognito user pools to 'Always'

References

[lama-ank]

If remember device is set to Always in AWS console, it is set back to No when tf is applied.

[WGriffing]

I could use this feature as well, but tf might be limited by what AWS CloudFormation exposes for Cognito User Pools.

See: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cognito-userpool-deviceconfiguration.html

Also, using

  lifecycle {
    ignore_changes = [device_configuration]
  }

within your aws_cognito_user_pool block is a way to get tf to not change the setting back to no. I've done some limited testing and this appears to be a viable workaround.

[lama-ank]

I see, thanks for checking out. We are using the workaround.

[chrispruitt]

This issue appears to be fixed explanation here -> #16799 (comment)

[ghost]

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]

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!