Using my own produced ssl key and cert (instead of the default one) create a better secure (encrypted) communication between the client and the cloudHSM.
Though this cannot be used to restrict access to cloudHSM from a specific client machine because the default key and cert can always be used from any other machine (along with the root CA).
Is that correct ???
How an access to HSM cluster can be restricted for a specific machine regardless the AWS infrastructure like security groups and private subnet... ? put aside the hsm credentials.
AWS 官方已更新 6 个月前
