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
Now that node_X.toml files contain only one secret privkey (there used to be also mnemonic and cross_client.pk but you have removed them), it becomes reasonable to move privkey from the toml file to an ENV variable.
We run Axon nodes in EKS cluster and use CSI Driver to mount secrets from AWS Secrets Manager into the pod.
Alternatives you've considered
Describe alternatives you've considered:
Even more robust solution would be to support the remote AWS signer (#1136), but it is unfeasible right now because AWS KMS does not support BLS cryptography.
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Contact Details
No response
Propose-a-new-feature
Now that
node_X.toml
files contain only one secretprivkey
(there used to be alsomnemonic
andcross_client.pk
but you have removed them), it becomes reasonable to moveprivkey
from the toml file to an ENV variable.We run Axon nodes in EKS cluster and use CSI Driver to mount secrets from AWS Secrets Manager into the pod.
Alternatives you've considered
Describe alternatives you've considered:
Even more robust solution would be to support the remote AWS signer (#1136), but it is unfeasible right now because AWS KMS does not support BLS cryptography.
Anything else?
No response
The text was updated successfully, but these errors were encountered: