From ba7e4e64c9e8ebe160b7bf2495b39a16ecf42222 Mon Sep 17 00:00:00 2001 From: calebAtIspot <136127709+calebAtIspot@users.noreply.github.com> Date: Mon, 17 Jun 2024 13:14:42 -0700 Subject: [PATCH] add note about secrets manager (#504) #267 added secret manager support, so I updated the readme to note that. That way people won't need to dig through the issues to figure out what the support status is. --- README.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 4633399..d8b7837 100644 --- a/README.md +++ b/README.md @@ -440,6 +440,14 @@ you can use `CHAMBER_AWS_REGION` to override just for chamber. If you'd like to use a custom SSM endpoint for chamber, you can use `CHAMBER_AWS_SSM_ENDPOINT` to override AWS default URL. +## AWS Secrets Manager +Chamber supports AWS Secrets Manager as an optional backend. For example: + +``` +chamber -b secretsmanager write myservice foo fah +chamber -b secretsmanager write myservice foo2 fah2 +``` + ## S3 Backend (Experimental) By default, chamber store secrets in AWS Parameter Store. We now also provide an @@ -512,4 +520,4 @@ a github release.