-
Notifications
You must be signed in to change notification settings - Fork 6
feat: add AWS signer configuration for sequencer signing #165
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.
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
feat: add AWS signer configuration for sequencer signing #165
Conversation
frisitano
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added some minor comments inline about moving the Signer creation logic into the SignerArgs.
frisitano
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks great! lgtm
frisitano
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a comment inline.
frisitano
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Overview
This PR extends the sequencer signing configuration by adding AWS KMS support alongside the existing private key file option. It introduces the
--signer.aws-kms-key-idparameter and implements mutually exclusive validation between the two signing methods to ensure exactly one is specified when the sequencer is enabled (unless in test mode).closes #163