AWS prescriptive-guidance documentation change
Summary
Removed leading forward slash from Secrets Manager naming convention example
Security assessment
The change is a minor formatting adjustment to a naming convention example, with no direct security implications or new security features documented
Diff
diff --git a/prescriptive-guidance/latest/secure-sensitive-data-secrets-manager-terraform/naming-convention.md index 444404dc5..11793fb52 100644 --- a/prescriptive-guidance/latest/secure-sensitive-data-secrets-manager-terraform/naming-convention.md +++ b/prescriptive-guidance/latest/secure-sensitive-data-secrets-manager-terraform/naming-convention.md @@ -7 +7 @@ -When you ingest and store secrets in AWS Secrets Manager, use a defined naming convention. For example, your naming convention might be `/<client name>/<dev or prod>/<project>/<version>`. Choosing a naming convention that makes sense for your organization. Use a hierarchical structure that progresses from most general information to most specific information. +When you ingest and store secrets in AWS Secrets Manager, use a defined naming convention. For example, your naming convention might be `<client name>/<dev or prod>/<project>/<version>`. Choosing a naming convention that makes sense for your organization. Use a hierarchical structure that progresses from most general information to most specific information.