AWS m2 documentation change
Summary
Added JHDB database secret configuration documentation with Secrets Manager integration
Security assessment
Documents secure credential management practices but doesn't address a specific vulnerability. Enhances security documentation without evidence of fixing an existing issue.
Diff
diff --git a/m2/latest/userguide/ba-runtime-config-app-secrets.md b/m2/latest/userguide/ba-runtime-config-app-secrets.md index 00bcbdaf6..650553b85 100644 --- a//m2/latest/userguide/ba-runtime-config-app-secrets.md +++ b//m2/latest/userguide/ba-runtime-config-app-secrets.md @@ -459,0 +460,28 @@ sslCipherKey | The IBM MQ SSL cipher suite. +### JHDB database + +The client `application-jhdb.yml` file can reference the secret ARNs for JHDB metadata databases. Each database connection requires a unique name and corresponding secret ARN containing the connection credentials. Database names are defined in a comma-separated list, with individual secret ARNs mapped to each database name. + + + spring: + aws: + jhdb: + cnxs: + datasources: + names: DBD1,DBD2 + DBD1: + secret: arn:aws:secretsmanager:XXXX + DBD2: + secret: arn:aws:secretsmanager:XXXX + +Supported client database secret keys: + +Secret key | Secret key description +---|--- +host | The host name. +port | The port. +dbname | The name of the database. +username | The username. +password | The password. +engine | Database engine: Postgres(now support Postgres only). +currentSchema | Specific schema to use. +