Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Configuration

Environment variables and service configuration for All ID.

Peer Service environment variables

Database configuration

Variable
Description
Example
Required

MYSQL_DATABASE

Database name for this peer

peer-default

Yes

MYSQL_IP

Database hostname or IP

database.cluster-xxx.us-east-1.rds.amazonaws.com

Yes

MYSQL_PORT

Database port

3306

Yes

MYSQL_USER

Database username (from secrets)

admin

Yes

MYSQL_PSWD

Database password (from secrets)

***

Yes

Multi-tenant setup: Each peer instance should use its own database. Database names follow the pattern peer-{name} (e.g., peer-default, peer-client-a, peer-client-b).

MYSQL_USER and MYSQL_PSWD should be loaded from a secrets management system (AWS Secrets Manager, HashiCorp Vault, Kubernetes Secrets, etc.) and never hardcoded.

REST API configuration

Variable
Description
Example
Required

REST_PORT

HTTP port for Peer API

8080

Yes

COMMAND_TIMEOUT

Request timeout in seconds

10

Yes

Facematch Service configuration

Variable
Description
Example
Required

FACEMATCH_IP

Facematch service hostname

facematch.allid

Yes

FACEMATCH_PORT

Facematch service port

8080

Yes

FACEMATCH_THRESHOLD

Matching threshold for facial recognition

1.2

Yes

The FACEMATCH_IP uses DNS-based service discovery. Configure your DNS or service discovery system to resolve this hostname to available Facematch instances.

Batch anonymization configuration

Variable
Description
Example
Required

BATCH_ANONYMIZATION_ENGINE_IMAGE_HASH

Image processing engine hash

ca10aef257b96ad49fd46c5df95856486530a08f

Yes

BATCH_ANONYMIZATION_ENGINE_MODEL_HASH

ML model hash for anonymization

adf712b1b839cc6d72f1059afb2c2b8fb68d995c

Yes

MAX_TASKS_ENABLED_PER_PEER

Maximum concurrent tasks per peer

10000

Yes

The hash values ensure integrity of the ML models. Do not modify these values unless provided by Certta with updated models.

RabbitMQ configuration (optional)

Variable
Description
Example
Required

ENABLE_RABBITMQ

Enable RabbitMQ integration

false

Yes

RABBITMQ_ANONYMIZATION_ERRORS_QUEUE_NAME

Error queue name

anonymization-errors

If enabled

RABBITMQ_ANONYMIZED_ASSETS_QUEUE_NAME

Anonymized assets queue

anonymized-assets

If enabled

RABBITMQ_NON_ANONYMIZED_ASSETS_QUEUE_NAME

Non-anonymized assets queue

non-anonymized-assets

If enabled

RabbitMQ is disabled by default. Enable only if you need asynchronous message processing for batch operations.

Redis cache configuration (optional)

Variable
Description
Example
Required

ENABLE_REDIS_CACHE

Enable Redis caching

false

Yes

ANONYMIZATION_CACHE_TTL

Cache TTL in milliseconds

300000 (5 minutes)

If enabled

Redis cache is disabled by default. Enable for improved performance in high-throughput scenarios.

Router Service configuration (required)

Variable
Description
Example
Required

ENABLE_ROUTER_COMMUNICATION

Enable Certta Router integration

true

Yes

ROUTER_REST_URL

Certta Router endpoint URL

https://mtls.us.prd.caf.io/v1/biometrics/facial-validation

Yes

ROUTER_PRIVATE_KEY

mTLS private key (from secrets)

-----BEGIN PRIVATE KEY-----\n...

Yes

ROUTER_CERTIFICATE

mTLS certificate (from secrets)

-----BEGIN CERTIFICATE-----\n...

Yes

mTLS Authentication: The Router communication requires mutual TLS (mTLS). The private key and certificate must be loaded from a secrets management system and never hardcoded.

Contact your Certta technical account manager to obtain the mTLS certificates for your environment.

Facematch Service environment variables

The Facematch Service requires minimal configuration.

Variable
Description
Default

PORT

HTTP port

8080

LOG_LEVEL

Logging level

INFO

The Facematch Service is designed to run with minimal configuration. It automatically loads ML models from the container image and listens on port 8080.

Service discovery

Services discover each other using DNS-based service discovery.

DNS names

Configure your service discovery system (e.g., AWS Cloud Map, Kubernetes DNS, Consul) to provide these DNS names:

Recommended DNS configuration:

  • DNS record type: A (IPv4)

  • TTL: 15 seconds (for fast failover)

Multi-tenant configuration

For multi-tenant deployments, each peer instance requires:

  • Unique MYSQL_DATABASE: e.g., peer-default, peer-client-a, peer-client-b

  • Unique Router mTLS certificate (loaded from separate secrets)

  • Unique DNS name in service discovery

  • Independent database with initialized schema

Next steps

Last updated