You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add optional ability to add custom_store_idl, i.e. AWS CloudHSM
Added in terraform/hashicorp/aws v4.33.0
Company is required for compliance to use key store that is controlled by us. We have been thru the discussion on how AWS stores keys and upper management still wants us to use CloudHSM. Tarraform resource aws_kms_key does have a custom_key_store_id (optional).
Can this be added so the custom_key_store_id can be provided (optional)?
This will be mostly used for EKS clusters and associated resources, i.e. Opensearch, etc.
The text was updated successfully, but these errors were encountered:
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.
Add optional ability to add custom_store_idl, i.e. AWS CloudHSM
Added in terraform/hashicorp/aws v4.33.0
Company is required for compliance to use key store that is controlled by us. We have been thru the discussion on how AWS stores keys and upper management still wants us to use CloudHSM. Tarraform resource aws_kms_key does have a custom_key_store_id (optional).
Can this be added so the custom_key_store_id can be provided (optional)?
This will be mostly used for EKS clusters and associated resources, i.e. Opensearch, etc.
The text was updated successfully, but these errors were encountered: