Your own managed clusters: mongodb://<username>:<password>@<host>[:port]/<authsource></authsource></host></password></username>
If you are leveraging the DNS seed list, use a connection string prefix of "mongodb+srv" rather than the standard mongodb. This will be required for Atlas.

authSource is the name of your database that contains the authentication information.

Database: The name of the database (must match).

Note: To connect with Internal, your data source must be publicly accessible, with SSL encryption enabled, and configured to accept connections from Internal’s IP addresses.

34.66.153.118/32
35.225.125.80/32

What happens when you connect

When you connect MongoDB to Internal, we'll generate the following for you automatically:

A list, insert, update, and delete function for each collection in the database (if the connecting user account has these privileges). List functions read data from your tables and allow you to display that data in components.

Note: Functions will not be generated if no primary keys are found in the connected database.

MongoDB Pipelines

In some cases, you may want to create a view that combines data from various collections or elevates nested JSON fields to top-level attributes. To accomplish this, create a new MongoDB Functions (a.k.a. MongoDB Pipeline).

Filtering and Sorting

While Internal enables filtering and sorting on all columns, we recommend indexing columns on large tables to improve performance. Supported operators vary by data type but include =, !=, <, <=",">, >=.</,>