This page outlines the recommended architecture for running MetaDefender ICAP Server with any Cloud Service Provider (CSP).
We provide diagrams for AWS, Azure, and GCP, where our product is available in their respective marketplaces. However, our products are cloud-agnostic and can be deployed to any CSP.
Infrastructure Options for MetaDefender ICAP Server
Using Compute Services
The appropriate infrastructure will vary depending on the number of instances where MetaDefender ICAP Server will be installed.
Options:
- Single Instance
- Multi-Instance with Autoscaling
Single Instance
To proceed, select the tab corresponding to the CSP where you intend to deploy MetaDefender ICAP Server
Multi-Instance with Autoscaling
Select the tab for the CSP where you want to deploy MetaDefender ICAP Server
Infrastructure Options for MetaDefender ICAP Server using Container Services
The possible infrastructure varies depending on the Cloud services used for hosting MetaDefender ICAP Server and how the required third-party tools are provisioned.
Options:
- Kubernetes Cluster with Customer-Managed Worker Nodes, utilizing either a Cloud PostgreSQL Service or third-party tools as Pods.
- Kubernetes Cluster with CSP-Managed Worker Nodes, utilizing either a Cloud PostgreSQL Service or third-party tools as Pods.
Customer Managed Worker Nodes
Select the tab for the CSP where you want to deploy MetaDefender Storage Security.
CSP-Managed Worker Nodes
Using above examples, include AWS Fargate or Azure Container Apps options for computing.
These are serverless compute engines for containers that allow you to run containerized applications without managing the underlying infrastructure.
These services run containers with certain limitations, such as CPU limits per instance or ephemeral storage, which may be required for some Linux packages.
Please check the system requirements before choosing this architecture.
We recommend deploying a database service from your Cloud Service Provider (CSP) for MetaDefender Core and MetaDefender ICAP Server
