'AWS Secrets Manager Design/Naming Conventions?
I'm trying to think of the best naming convention for storing AWS Secrets across different projects and files accessing different database. Essentially I'm removing some legacy code from many files with hard-coded credentials.
What is the best way to structure the path that the files will use to access secrets manager (ie. dev/scripts/script1 for one file, dev/scripts/script2 for another)? I don't think i can just use the name of the files since that can be the same across different projects.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|