re functionality altogether.

Backup secrets storeA backup secrets store back-end may be configured for high-availability and backup purposes. or as an intermediate step in the process of migrating secrets to a different external location or secrets manager provider.

To configure a backup secrets store in the Docker container, use the same approach and instructions documented for the primary secrets store, but set the **ZENML\_BACKUP\_SECRETS\_STORE\*** environment variables instead of **ZENML\_SECRETS\_STORE\***, e.g.:

ZENML_BACKUP_SECRETS_STORE_TYPE: aws

ZENML_BACKUP_SECRETS_STORE_AUTH_METHOD: secret-key

ZENML_BACKUP_SECRETS_STORE_AUTH_CONFIG: '{"aws_access_key_id":"<aws-key-id>", "aws_secret_access_key","<aws-secret-key>","role_arn": "<aws-role-arn>"}`'

Advanced server configuration options

These configuration options are not required for most use cases, but can be useful in certain scenarios that require mirroring the same ZenML server configuration across multiple container instances (e.g. a Kubernetes deployment with multiple replicas):

ZENML_SERVER_JWT_SECRET_KEY: This is a secret key used to sign JWT tokens used for authentication. If not explicitly set, a random key is generated automatically by the server on startup and stored in the server's global configuration. This should be set to a random string with a recommended length of at least 32 characters, e.g.:Copyfrom secrets import token_hex
token_hex(32)or:Copyopenssl rand -hex 32

The environment variables starting with ZENML_SERVER_SECURE_HEADERS_* can be used to enable, disable or set custom values for security headers in the ZenML server's HTTP responses. The following values can be set for any of the supported secure headers configuration options:

enabled, on, true or yes - enables the secure header with the default value.

disabled, off, false, none or no - disables the secure header entirely, so that it is not set in the ZenML server's HTTP responses.

any other value - sets the secure header to the specified value.