-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
fb16e46
commit 493ac16
Showing
4 changed files
with
86 additions
and
11 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
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,26 @@ | ||
## Using AWS Secret Manager as a backend for cerberus | ||
You can use AWS Secret Manager as a backend for cerberus. To use AWS Secret Manager as a backend, you need to set the `STORAGE_TYPE` environment variable to `aws-secrets-manager`. | ||
All the public keys are stored in `cerberus/<pub-key-hex>` format. | ||
|
||
You have two options for authenticating with AWS Secret Manager: | ||
### Environment variables | ||
You will need to set the `AWS_AUTHENTICATION_MODE` environment variable to `environment`. This is the default mode. You will also need to set the `AWS_REGION`. If you are using a profile, you can set the `AWS_PROFILE` environment variable. If you are using the default profile, you do not need to set the `AWS_PROFILE` environment variable. | ||
|
||
Example | ||
```bash | ||
cerberus \ | ||
--storage-type aws-secrets-manager \ | ||
--aws-region us-east-2 \ | ||
--aws-profile SomeProfile | ||
``` | ||
### Specified | ||
You will need to set the `AWS_REGION`, `AWS_ACCESS_KEY_ID`, and `AWS_SECRET_ACCESS_KEY` environment variables. | ||
|
||
Example | ||
```bash | ||
cerberus \ | ||
--storage-type aws-secrets-manager \ | ||
--aws-region us-east-2 \ | ||
--aws-access-key-id SomeAccessKey \ | ||
--aws-secret-access-key SomeSecretKey | ||
``` |
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,11 @@ | ||
## Using Filesystem as a backend for cerberus | ||
You can use Filesystem as a backend for cerberus. To use Filesystem as a backend, you need to set the `STORAGE_TYPE` environment variable to `filesystem`. | ||
|
||
You will need to setup the storage directory where the private keys will be stored. By default, the private keys are stored in the `./data/keystore` directory. You can change this by setting the `KEYSTORE_DIR` environment variable. | ||
|
||
Example | ||
```bash | ||
cerberus \ | ||
--storage-type filesystem \ | ||
--keystore-dir /path/to/keystore | ||
``` |