How to Configure MetaDefender Core AMI from AWS Marketplace for the POC

Scenario

When you want to deploy MetaDefender Core using the AWS Marketplace AMI may encounter difficulties with initial configuration steps, including database setup, license activation, EC2 disk provisioning, and concerns regarding temporary file storage under the /tmp directory.

Resolution

This article outlines the recommended configuration steps for setting up the MetaDefender Core AMI in AWS for proof-of-concept (POC) use.

Configuration Steps

1. Use the POC-Specific AMI

Deploy the AMI designed specifically for POC scenarios. This AMI is configured with:

• DB_TYPE=local
• DB_MODE=4

These settings enable a built-in local database for simplified setup.

2. Login Credentials

• Default Access: Use the username admin and the EC2 instance ID as the default password.
• Custom Credentials: Optionally, define a custom username and password by specifying them in the EC2 instance’s user-data field at launch time.

3. License Activation

To activate your license during provisioning:

• Add your LICENSE_KEY in the user-data field.
• This triggers automatic activation or deactivation of the license upon instance startup.

4. Disk Provisioning

• No need to manually configure separate volumes for the MetaDefender Core application and the PostgreSQL database.
• The AMI is preconfigured with appropriate disk settings for streamlined deployment.

5. Temporary File Storage

• Files temporarily stored under /tmp are automatically removed after processing.
• No manual cleanup is required.

Troubleshooting Notes

• This AMI is intended for POC purposes and is limited in its configurability.
• For production deployments or environments requiring advanced customization (e.g., external databases, custom network configurations), consider using other deployment options such as containerized installations or manual configuration on a base EC2 instance.