How to disable the Local MongoDB when using an external Database?

Overview

If you prefer to connect the MetaDefender Storage Security (MDSS) application to your own remote MongoDB database server, you can disable the built-in MongoDB container and its related references by editing the Docker Compose files. While the bundled MongoDB service consumes minimal resources when idle, you can still reclaim those resources by following the steps below.

Instructions

1. Stop the MDSS Application

Before making any configuration changes, stop the MDSS services:

sudo mdss -c stop

2. Disable the Built-in MongoDB Container

Open the following file in a text editor: /etc/mdss/docker-compose.main.yml

Locate the mongodb service section and add the following:

profiles: - disabled

3. Modify Service Dependencies

In the same file (/etc/mdss/docker-compose.main.yml), navigate to the rabbitmq service section and comment out the MongoDB dependency:

# depends_on: # - mongodb

Then, open the file: /etc/mdss/docker-compose.mdss.yml, find the mongomigrations section and comment out the MongoDB dependency there as well:

# depends_on: # - mongodb

4. Start the MDSS Application

Once all modifications are complete, start the MDSS services again:

sudo mdss -c start

Verification

After restarting, verify that:

• MDSS is running without the internal MongoDB container.
• The application is successfully connected to your external MongoDB server.

You can check logs or test basic application functionality to ensure a proper connection.