Fixing Documentation issues with Secrets Manager (#183)

* Fixing Documentation issues with Secrets Manager

* Fixing Documentation issues with Secrets Manager
This commit is contained in:
Ela AWS
2023-06-16 11:25:32 -04:00
committed by GitHub
parent de8c1233ee
commit c705238f0c
4 changed files with 5 additions and 5 deletions
+1 -1
View File
@@ -9,12 +9,12 @@ Our goal is to make it easier to use AWS Open Source Observability Services.
The core team include the following people:
* Abhi Khanna
* Elamaran Shanmugam
* Imaya Kumar Jagannathan
* Jerome DECQ
* Kevin Lewin
* Michael Hausenblas
* Munish Dabra
* Ramesh Kumar Venkatraman
* Rodrigue Koffi
* Toshal Dudhwhala
* Vara Bonthu
+2 -2
View File
@@ -93,7 +93,7 @@ Ensure you have necessary IAM permissions (`CreateWorkspaceApiKey, DeleteWorkspa
!!! note
Starting version v2.5.x and above, we use Grafana Operator and External Secrets to
manage Grafana contents. Your API Key will be stored securely on AWS Secrets Manager
manage Grafana contents. Your API Key will be stored securely on AWS SSM Parameter Store
and the Grafana Operator will use it to sync dashboards, folders and data sources.
Read more [here](https://aws-observability.github.io/terraform-aws-observability-accelerator/concepts/).
@@ -231,7 +231,7 @@ export GO_AMG_API_KEY=$(aws grafana create-workspace-api-key \
--output text)
```
- Finally, update the Grafana API key secret in AWS Secrets Manager using the above new Grafana API key:
- Finally, update the Grafana API key secret in AWS SSM Parameter Store using the above new Grafana API key:
```bash
aws aws ssm put-parameter \