This Guidance shows how to deploy a secure, scalable, and cost-efficient blockchain key management solution for blockchain validation workloads like Ethereum 2.0 proof-of-stake networks.
So we have another issue. When we try to add new validator key into Dynamo DB table and assign UUID to ID, it doesn't update running web3signer.
We tried rebooting instances with enclaves which didn't fix issue, but instead created a new one.
Upon checking, lambda function (operation": "web3signer_public_keys"), after the instance re-boot it throws the following error:
Please advise.
how to add new keys to running instances/web3 signer process;
how to quickly address this kind of TLS errors. (P.S my current solution is to run CDK destroy and then deploy again.
And a follow-up question, how in general can we re-start the service. for instance, we want to remove our validator stake?
Can't find instruction on how to manage it.
Hi David @dpdornseifer
So we have another issue. When we try to add new validator key into Dynamo DB table and assign UUID to ID, it doesn't update running web3signer.
We tried rebooting instances with enclaves which didn't fix issue, but instead created a new one. Upon checking, lambda function (operation": "web3signer_public_keys"), after the instance re-boot it throws the following error:
Please advise.