-
Notifications
You must be signed in to change notification settings - Fork 60
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into fr/readmeUpdates
- Loading branch information
Showing
56 changed files
with
809 additions
and
255 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
Web3-API supports AWS KMS for signing & sending transactions over any EVM chain. This is a guide on how to set up AWS KMS for Web3-API. | ||
|
||
### Steps to set up AWS KMS | ||
|
||
1. Create IAM user with programmatic access, see [here](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_create.html#id_users_create_console) for more details. | ||
2. Add create, get, read permission to KMS, see [here](https://docs.aws.amazon.com/kms/latest/developerguide/control-access.html) for more details. | ||
3. Create a AWS KMS key, see [here](https://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html) for more details. or, you can use the `/wallet/create` to create a key. | ||
|
||
NOTE: | ||
|
||
If you are creating the key yourself on AWS KMS Console, then please select the below config to create a key with sign permission. | ||
|
||
``` | ||
Key Type: Asymmetric | ||
Key Spec: ECC_SECG_P256K1 | ||
Key Usage: Sign and verify | ||
``` | ||
|
||
Once you create the key above, you can use `/wallet/add` and send details on the end-point to create the wallet | ||
|
||
### Set up Web3-API with AWS KMS | ||
|
||
Create a `.env` file in the root directory of the project and add the below details. | ||
|
||
``` | ||
# Required for AWS Auth | ||
AWS_ACCESS_KEY_ID=<aws_access_key_id> | ||
AWS_SECRET_ACCESS_KEY=<aws_secret_access_key> | ||
AWS_REGION=<aws_region> | ||
# Required for AWS KMS Admin Wallet | ||
AWS_KMS_KEY_ID=<kms_key_id> | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
Web3-API supports Google KMS for signing & sending transactions over any EVM chain. This is a guide on how to set up Google KMS for Web3-API. | ||
|
||
### Steps to set up Google KMS | ||
|
||
1. Enable Google KMS API for your Google project, see [here](https://cloud.google.com/kms/docs/create-encryption-keys#before-you-begin) for more details. | ||
2. Create a Service Account (here)[https://cloud.google.com/iam/docs/service-accounts-create] and create a key under this service account and download the JSON file. This JSON file details will be used to authenticate with Google KMS. | ||
3. Add the below permissions to the service account created in step 2. | ||
|
||
``` | ||
Cloud KMS Admin | ||
Cloud KMS CryptoKey Signer/Verifier | ||
``` | ||
|
||
4. Create a keyring in Google KMS, see [here](https://cloud.google.com/kms/docs/create-key-ring) for more details. | ||
|
||
Optional: Create a key in the keyring, see [here](https://cloud.google.com/kms/docs/create-key) for more details. or, you can use the `/wallet/create` to create a key in the keyring. | ||
|
||
### Set up Web3-API with Google KMS | ||
|
||
Create a `.env` file in the root directory of the project and add the below details. | ||
|
||
``` | ||
# Required for Google Auth | ||
GOOGLE_APPLICATION_CREDENTIAL_EMAIL=<client_email_from_download_service_account_json> | ||
GOOGLE_APPLICATION_CREDENTIAL_PRIVATE_KEY=<private_key_from_download_service_account_json> | ||
# Required for Google KMS | ||
GOOGLE_APPLICATION_PROJECT_ID=<google_project_id> | ||
GOOGLE_KMS_KEY_RING_ID=<key_ring_id> | ||
GOOGLE_KMS_LOCATION_ID=<location_of_key_ring> | ||
GOOGLE_KMS_CRYPTO_KEY_ID=<kms_key_id> # If created on Google Console | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.