A provider class should be implemented to support issue Consensys/web3signer#531.

Tasks:

• Implement CacheableAwsSecretsManagerProvider class to support either creating new or serving cached AWS secrets managers based on access key ID.
• Unit tests to validate cache hit or miss and clearing

Design a signing service library that makes use of ethsigner and eth2signer to be a generic signing service.

The signing service is platform/usecase/crypto agnostic

• test fixtures are not published to cloudsmith maven repo. signing-secp256k1-impl-1.0.15-test-fixtures.jar should be available but it is not.
• Signer's test-fixtures are are used by tests in web3signer.
• reach out to cloudsmith support to report/fix the issue
• Update signer version in web3signer to resolve latest version from cloudsmith

Prysm generates EIP2335 keystores with no path property but signers requires path to be present even though it doesn't actually get used.

UUID is also marked as required but doesn't seem to actually be required.

The AWS SDK should be able to authenticate a secrets manager connection using the default region provider chain

Tasks

• Implement createAwsSecretsManager method (no params) that initializes and returns a SecretsManager connection using the environment's region.

Retrieve a secret from AWS secret manager.

Tasks

• Key retrieval from AWS in signers

Acceptance Criteria

• Key name should be configurable
• Acceptance test to ensure that Azure secret can be retrieved

Notes

• Don’t want multiple clients in memory for the same vault instance
• Needs to be able keys from multiple differently configured AWS secret manager instances
• Large number of keys are not loaded simultaneously i.e. don't make 1000 http requests at once to retrieve secrets