aws_fsx_lustre_file_system specify custom KMS Key

[cmbrad]

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

New or Affected Resource(s)

FSX for Lustre now supports using custom KMS keys for encryption at rest. Currently the resource always uses the default FSX key, but it would be good to allow specifying custom customer managed keys. Only valid where deployment_type = "PERSISTENT_1"

• aws_fsx_lustre_file_system

Potential Terraform Configuration

resource "aws_fsx_lustre_file_system" "fsx" {
   # ...
   kms_key_id= "alias of encryption key"
}

References

• r/asg: Fix TestAccAWSAutoScalingGroup_VpcUpdates #1218
• https://docs.aws.amazon.com/fsx/latest/LustreGuide/getting-started-step1.html
• https://docs.aws.amazon.com/fsx/latest/LustreGuide/encryption-at-rest.html
• https://docs.aws.amazon.com/fsx/latest/LustreGuide/FSXKMS.html
• https://docs.aws.amazon.com/fsx/latest/APIReference/API_CreateFileSystem.html

[bflad]

Support for the kms_key_id argument in the aws_fsx_lustre_file_system resource has been merged and will release with version 3.8.0 of the Terraform AWS Provider, later this week. Thanks to @nikhil-goenka for the implementation. 👍

[ghost]

This has been released in version 3.8.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!