Deploy with an External MongoDB Cluster

due to ongoing incompatibilities, turbine does not support using amazon documentdb as an option for external mongodb cluster deployment there are two primary deployment models for using an external mongodb cluster with turbine self hosted mongodb cluster mongodb atlas the physical location of the external mongo deployment, as it pertains to latency between the turbine cluster and the standalone mongo instance, performs best with a latency delay of less than 5 milliseconds be aware that with every added millisecond of latency, turbine's performance drops linearly general requirements the mongodb version is v6 0 20 for information about the mongodb version used in previous releases for any external deployment, see tp installer release notes https //support swimlane com/support/solutions/folders/8000090778 self hosted mongodb cluster customer maintained mongodb clusters are supported as long as the external mongodb cluster meets the requirements listed in the system requirements for an existing cluster install docid\ snkpyftncien7nwfs7tfp for existing clusters swimlane requires that you name your databases swimlane , swimlanehistory and turbine in your deployment in each database, also create a swimlane user and ensure that it is assigned the dbowner role mongodb atlas you can use mongodb atlas as an external mongodb cluster as long as the cluster has been configured to use a compute tier that aligns with the system requirements for system requirements for an existing cluster install docid\ snkpyftncien7nwfs7tfp or system requirements for an embedded cluster install docid 9lxricxlm1t14ydlkt4zr cluster installations dedicated m40 clusters are the minimum compute tier required for an external mongodb cluster after creating your atlas cluster, you must create three databases swimlane requires that you name your databases swimlane , swimlanehistory and turbine in your deployment in each database, also create a swimlane user users, databases, and roles are all managed through the atlas ui atlas does not have a "dbowner" role that would be used in self hosted clusters instead, your created users should be assigned the specific advanced privileges dbadmin and readwrite additionally, you can scope the permissions of each user to their respective databases, although it is not required the built in role "read and write to any database" is not sufficient, as turbine requires the ability to create indexes in mongodb, which is a dbadmin privilege configuring external mongo in the turbine platform installer when you select the use an external mongodb deployment option, the tpi ui hides all of the embedded mongo options and displays these sections mongodb swimlane database settings , mongodb swimlane history database settings and mongodb turbine database settings both of these sections set their respective database's configuration and contain the same options as described here mongodb prefix describes the prefix of the mongodb connection string the default value is mongodb // , however mongodb+srv // is also a valid prefix this prefix is common when using mongodb atlas mongodb username the username for the user associated with the relevant database that is being configured, either swimlane or swimlanehistory or turbine mongodb password the password for the user associated with the relevant database that's being configured, either swimlane or swimlanehistory or turbine mongodb hostname list the hostname or set of hostnames for the mongodb cluster for multi node clusters, this is usually in the form of a comma separated list of hostnames and ports in atlas deployments, this can be the srv record for the cluster provided by the atlas ui mongodb database the database name relevant to the database that's being configured, either swimlane or swimlanehistory or turbine upload tls certificates to use in the mongodb connection uri options enables the uploading of a ca certificate if the mongodb cluster uses an internal ca mongodb connection options provides additional options to the connection string currently, the only supported options for the swimlane and swimlane history database are ssl and sslverifycertificates the turbine database supported optins are tls and tlsallowinvalidcertificates