During the Atlas start phase of MongoDB setup, DSI establishes an SSH connection to a workload client and executes mongod --version (code) to obtain the version and gitVersion of mongod. These version numbers are then used to create a custom Atlas build. This process has two implications:

• The provisioning of Atlas clusters is dependent on the provisioning of workload clients. This interdependence complicated the solution for DEVPROD-3880, which required the provisioning of a temporary workload client to execute mongod --version. After the Atlas cluster was provisioned, the temporary workload client was torn down and a new one was set up in the designated Availability Zone.

• The MongoDB binary used for the workload client must be identical to the one used for the server (i.e., the Atlas cluster).

I propose incorporating a mongod metadata information file into the supplementary info package. This would allow DSI to extract version and gitVersion information directly from the file, eliminating the need for a temporary workload client.

Furthermore, if possible, I recommend including the mongod binary OS and CPU architecture details in this file. This would obviate the need to extract such information from tarball names.