Skip to content

Add signer-proxy as a recommended solution for AWS KMS or YubiHSM key management #1280

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add signer-proxy as a recommended solution for AWS KMS or YubiHSM key management #1280

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions pages/builders/chain-operators/management/key-management.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,10 @@ Key Management Systems (KMS) that can work with your developer operations
configurations. This can be used in conjunction with the `eth_signTransaction`
RPC method.

If you intend to manage your keys using AWS KMS or YubiHSM2, you can use [signer-proxy](https://github.com/upnodedev/signer-proxy).

[signer-proxy](https://github.com/upnodedev/signer-proxy) is an open-source tool that connects to your AWS KMS or YubiHSM2 backend and exposes an endpoint compatible with the `eth_signTransaction` RPC method.

<Callout type="info">
You can take a look at the signer client [source code](https://github.com/ethereum-optimism/optimism/blob/develop/op-service/signer/client.go)
if you're interested in what's happening under the hood.
Expand Down