An Ethereum based signed that derivces addresses and signs transactions using AWS KMS.
The following will walk you through using the KMS Signer in your application.
Install the NPM Package by running the following in your terminal
npm add @dirtroad/kms-signerThe package is currently setup to use AWS Key Management Service to handle the keys associated with a given signer. If you do not have an AWS account, you will need one. Additionally, while the actual amount can vary, visit the pricing page for KMS and other AWS services to understand possible costs associated with using this package in any environment.
Start by logging into AWS and then follow the directions below:
- Search for KMS in the Search Bar
- Select CREATE KEY
- For the Key type select Asymmetric
- For the Key usage select Sign and Verify
- For the Key spec select the last option -- ECC_SECG_P256K1
- If you plan to use this key during develompent, then you can proceed to the next step. If using in production and you want to replicate the key across multiple regions, click Advanced Options and then select Multi-Region key
- Fill in the labels according to your project and add tags as you see fit
- If you already have IAM Roles setup, you can assgin Key Administrative Permissions or Key Usage Permissions there. If not, proceed to the review step and continue with this guide.
In order to properly access the recently creating key, copy the ARN from the main screen and head over to IAM in the AWS Console.
- Create a Group
- Create a User -- reminder to save the credentials for usage
- Add the User to the Group
- Create a Policy. The policy should be for KMS, and allow the policy inheritor to -- Sign and ** GetPublicKey**.
- For resources, you can now copy in the ARN and it will mean the policy only works for the specific key creating in the previous step.
- Add the Policy to the Group (recommended by AWS) or to the User
After the steps above, you should now be able to seed in the AccessKeyId and the SecretAccessKey from the created IAM user and use the KeyId from the KMS key to access and sign transactions.
To contribute to this repository, fork and clone the repo from GitHub and follow the development guide below.
git clone [email protected]/Dirt-Road-Development/kms-signer && cd kms-signernpm installBranches should follow the naming conventions seen here:
| Contribution Type | Branch Prefix |
|---|---|
| Bug Fix | bug/ |
| Hot Fix | hotfix/ |
| Feature | feature/ |
| Documentation | docs/ |
| Tests | tests/ |
|
Check out a GitHub branch by running the following command:
git checkout -b feature/this-is-a-new-featureWhen in active development on a branch you should actively push changes up to your own GitHub repo (fork).
Once your code is ready to be reviewed, create a Pull Request into the main Dirt Road Development main branch and request TheGreatAxios to review the PR.
Please add accompanying tests if possible. NOTE -- This repo currently does not have any tests.
This codebase is released under the MIT License. See the License here. The KMS Signer and code is WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
The following repository is only possible thanks to a couple of amazing authors:
Rumble Fish Blockchain Development for the follwoing repositories:
RJ Chow for the follwowing repositories: