Skip to main content
Version: v2.0 (deprecated)

Managed PostgreSQL and Neo4j

For production deployment of Deepfence Management Console, we recommend using cloud/vendor managed PostgreSQL and Neo4j services.

Neo4j

Please use the following settings to configure the Neo4j AuraDB Professional / Enterprise service

OptionRecommended Value
Memory8GB
CPU2 CPU
Storage16GB

In docker-compose.yml, set the values for postgresql accordingly.

x-service-variables: &common-creds
DEEPFENCE_NEO4J_USER: neo4j
DEEPFENCE_NEO4J_PASSWORD: <password>
NEO4J_AUTH: neo4j/<password>
DEEPFENCE_NEO4J_BOLT_PORT: 7687
DEEPFENCE_NEO4J_HOST: abcdefgh.databases.neo4j.io

PostgreSQL

AWS RDS

Please use the following settings to configure the Elasticsearch service

OptionRecommended Value
EnginePostgreSQL
Version13.7-R1 or above
AvailabilitySingle DB instance / Multi-AZ DB instance
CredentialsSet username and password
DB instance classdb.m6i.large / db.t3.medium or better
Storage typeProvisioned IOPS SSD
Allocated storage>= 100
Provisioned IOPS>= 3000
Public accessNo (provide access only to management console nodes)
Database authenticationPassword authentication
Initial database namedeepfence

In docker-compose.yml, set the values for postgresql accordingly.

x-service-variables: &common-creds
DEEPFENCE_POSTGRES_USER_DB_USER: postgres
DEEPFENCE_POSTGRES_USER_DB_PASSWORD: <password>
DEEPFENCE_POSTGRES_USER_DB_HOST: pg-db-1.aaaaaa.us-east-1.rds.amazonaws.com
DEEPFENCE_POSTGRES_USER_DB_NAME: deepfence
DEEPFENCE_POSTGRES_USER_DB_PORT: 5432
DEEPFENCE_POSTGRES_USER_DB_SSLMODE: disable