Troubleshooting and Maintenance
For troubleshooting MetaDefender ICAP with Kubernetes deployment , please refer to the following guides:
- Troubleshooting K8S (installation, logging, cluster management tools)
For troubleshooting MetaDefender ICAP with EC2 deployment , please refer to the following guides:
- How to read the MetaDefender ICAP Server log to read(installation, logging, node management)
- AWS Database Troubleshooting (AWS Docs for RDS)
Routine Maintenance
Always update the MetaDefender deployment with the new versions published either on:
- portal.opswat.com > Products section
- AWS Marketplace
Release Notes are available here.
If you are deploying MetaDefender in your own AWS environment, the AWS service limits will not impact the product. A potential issue that can be caused by AWS service is using a lower-tier EC2 type than is recommended. Please see the Costs section above for details on which EC2 instance types we recommend for MetaDefender. Network bandwidth and EBS/General SSD IOPS can become a limitation in high-throughput environments. The solution to this is to simply use higher tier machines such as ones with 20+Gbps network bandwidth and moving to a provisioned IOPS (io2) disk(s).
Emergency Maintenance
In case of any availability failures of an AWS Service, recommended actions would be to pass the load to another MetaDefender instances, preferably deployed in a different AZ than the one affected. Any analysis in progress submitted to MetaDefender will be considered lost. However, is highly recommended to build a resilient system that won't rely on MetaDefender to recover the pending jobs, but to be managed by a queueing mechanism (e.g. AWS SQS). See Backup and Recovery suggested deployment scenarios.