AWS documentdb: Document combined engine version and patch version output format
Summary
Explains that from Amazon DocumentDB 5.0.2 and 8.0.2, db.runCommand({getEngineVersion: 1}) returns engine version and patch version as a single combined string, and advises updating scripts/monitoring that parse the output.
Security assessment
This is a version-string format clarification for maintenance/monitoring tooling; it contains no security guidance, vulnerability reference, or configuration with security impact.
Evidence
+Starting with Amazon DocumentDB 5.0.2 and 8.0.2, `db.runCommand({getEngineVersion: 1})` returns the engine version and the engine patch version as a single string in the form ``engine-version`+`engine-patch-version``. For example, a cluster on Amazon DocumentDB 5.0.2 returns `5.0.2+3.0.12345`, and a cluster on 8.0.2 returns `8.0.2+4.0.12345`. Clusters on earlier versions return the engine patch version on its own, such as `3.0.12345`.
Diff
diff --git a/documentdb/latest/devguide/db-instance-maintain.md b/documentdb/latest/devguide/db-instance-maintain.md index 4015b3c4b..7c9eb538f 100644 --- a//documentdb/latest/devguide/db-instance-maintain.md +++ b//documentdb/latest/devguide/db-instance-maintain.md @@ -91 +91 @@ Amazon DocumentDB uses two separate version identifiers: -You can determine the engine version from the engine patch version's prefix, as shown in the following table. +When the engine patch version appears on its own, you can determine the engine version from its prefix, as shown in the following table. @@ -101,0 +102,6 @@ To check the patch version your cluster is running, connect and run `db.runComma +###### Note + +Starting with Amazon DocumentDB 5.0.2 and 8.0.2, `db.runCommand({getEngineVersion: 1})` returns the engine version and the engine patch version as a single string in the form ``engine-version`+`engine-patch-version``. For example, a cluster on Amazon DocumentDB 5.0.2 returns `5.0.2+3.0.12345`, and a cluster on 8.0.2 returns `8.0.2+4.0.12345`. Clusters on earlier versions return the engine patch version on its own, such as `3.0.12345`. + +If you have scripts or monitoring that parse the output of `getEngineVersion`, update them to handle the combined format. +