Architecture Examples in CSPs
This page explains what are the architecture recommended for running MetaDefender ICAP Server using in any Cloud Service Provider. We include diagrams of AWS, Azure and GCP that is where we are present in their respective marketplace. However, we are not Cloud dependent and our products can be deployed to all the CSPs.
Infrastructure Options for MetaDefender ICAP using Compute services
The possible infrastructure vary depending on what are the number of instances where MetaDefender ICAP Server will be installed
Options:
- Single Instance
- Multi-Instance with Autoscaling.
Single Instance
Select the Tab depending on the CSP where you want to deploy MetaDefender ICAP
Multi-Instance with Autoscaling
Select the Tab depending on the CSP where you want to deploy MetaDefender ICAP
Infrastructure Options for MetaDefender Core using Container Services
The possible infrastructure vary depending on what are the Cloud services for hosting MetaDefender ICAP and how the PostgreSQL database is provisioned.
Options:
- Kubernetes Cluster with Customer Managed Worker Nodes + Cloud PostgreSQL Service or PostgreSQL Pod
- Kubernetes Cluster with CSP Managed Worker Nodes + Cloud PostgreSQL Service or PostgreSQL Pod
Customer´s Managed Worker Nodes
Select the Tab depending on the CSP where you want to deploy MetaDefender ICAP
EC2 Instances + AWS RDS or PostgreSQL Pod
CSP´s Managed Worker Nodes
Select the Tab depending on the CSP where you want to deploy MetaDefender ICAP
AWS Fargate + AWS RDS / PostgreSQL Pod
We offer a Terraform project for provisioning all the resources or a provisioning script that depending on the selection, we automatically provision the cluster for you and install the K8S components needed for having MetaDefender Core and MetaDefender ICAP Server services deployed.