Managed shared services
Usage
- Basic deployment with managed services
- Advanced deployment with managed services
Overview
This deployment type builds upon the single-instance deployment and serves as an alternative to the self-hosted shared services option. Recognizing the importance of scalability, it also covers the deployment of multiple instances of Storage Security to enhance capacity and reliability.
Deploying multiple instances of MetaDefender Storage Security
After successfully deploying and configuring a single instance, a new virtual machine (VM) can be provisioned within the same network. Here, Storage Security can be installed using the same installer package as the initial setup. This new installation should be configured to utilize the same services as the first by following the configuration steps outlined here: Configure Storage Security to connect to the external services
This process can be replicated as many times as needed to meet performance and redundancy requirements. Each new instance replicates all services and operates identically to the initial setup, allowing for access to the same web user interface for configuration and initiating scans.
Accessing MDSS when deployed on multiple instances
Since each instance utilizes the same database and provides the same web user interface, they can all be consolidated behind a single entry point using load balancing. Although a load balancer is not essential for routine scans (non-event-based), it becomes necessary to ensure high availability for event-based, real-time scanning scenarios.
In a cloud environment, load balancers can be provisioned, configured, and managed by the cloud provider, effectively distributing traffic across all instances. Conversely, in an on-premises setup, load balancers must be manually deployed. There are various solutions available for this, including:
- NGINX: Load Balancer
- HAProxy: HAProxy Products Documentation
- Traefik: Routing & Load Balancing Overview |Traefik Docs - Traefik
Managed services configuration
Managed services (from AWS, Azure or Google Cloud) are drop-in replacements to the self-hosted services and can be configured in MDSS in the same way although the terminology might differ slightly from one cloud provider to another.
For example here is how to replace all external services with their equivalent from AWS: Managed Services configuration in AWS
Options from other cloud providers:
MongoDB:
- CosmosDB from Azure: Introduction/Overview - Azure Cosmos DB for MongoDB
- MongoDB Atlas: MongoDB Atlas Database | Multi-Cloud Database Service
Redis:
- Azure Cache for Redis: Azure Cache for Redis | Microsoft Azure
RabbitMQ:
- CloudAMQP: CloudAMQP - Queue starts here.