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
Add bulk loading of AWS secp256k1 keys in web3signer. This mirrors the bulk loading functionality of BLS signing in Web3signer to load multiple keys from a single configuration.
Add AWS param to the Eth1Config
Create a secp AWS bulk loader to retrieve key names and create ArtifactSigners
Add support to KMS tags
Update runner to secp AWS bulk loader
Update runner to add healthcheck for AWS bulk loading
Acceptance test (see acceptance-tests/src/test/java/tech/pegasys/web3signer/tests/bulkloading/AwsSecretsManagerAcceptanceTest.java)
Performance test bulk loading to ensure is comparable to secrets manager bulk loading used for BLS
The text was updated successfully, but these errors were encountered:
Performance test with 10, 1000 and 10000 keys. In AWS the keys aren't deleted immediately and are marked for deletion. And the API to list keys also returns keys marked for deletion so each test run affects further tests to a degree. I've included the number of keys marked for deletion in the test results too so this can be factored into the results.
Add bulk loading of AWS secp256k1 keys in web3signer. This mirrors the bulk loading functionality of BLS signing in Web3signer to load multiple keys from a single configuration.
The text was updated successfully, but these errors were encountered: