Skip to main content

Advanced parameters for Aiven for Dragonfly®

See the configuration options available for Aiven for Dragonfly®:

Parameter
  • default: 0.0.0.0/0

IP filter

Allow incoming connections from CIDR address block, e.g. '10.20.0.0/16'

service_log

boolean,null

Service logging

Store logs for the service so that they are available in the HTTP API and console.

static_ips

boolean

Static IP addresses

Use static public IP addresses

Allow access to selected service ports from private networks

Allow clients to connect to prometheus with a DNS name that always resolves to the service's private IP addresses. Only available in certain network locations

Allow clients to connect to dragonfly with a DNS name that always resolves to the service's private IP addresses. Only available in certain network locations

Allow access to selected service components through Privatelink

Enable prometheus

Enable dragonfly

Allow access to selected service ports from the public Internet

Allow clients to connect to prometheus from the public internet for service nodes that are in a project VPC or another type of private network

Allow clients to connect to dragonfly from the public internet for service nodes that are in a project VPC or another type of private network

migration

object,null

Migrate data from existing server

Hostname or IP address of the server where to migrate data from

  • min: 1
  • max: 65535

Port number of the server where to migrate data from

Password for authentication with the server where to migrate data from

  • default: true

The server where to migrate data from is secured with SSL

User name for authentication with the server where to migrate data from

Database name for bootstrapping the initial connection

Comma-separated list of databases, which should be ignored during migration (supported by MySQL and PostgreSQL only at the moment)

Comma-separated list of database roles, which should be ignored during migration (supported by PostgreSQL only at the moment)

The migration method to be used (currently supported only by Redis, Dragonfly, MySQL and PostgreSQL service types)

Name of the basebackup to restore in forked service

  • default: true

Require SSL to access Dragonfly

cache_mode

boolean

Evict entries when getting close to maxmemory limit

Name of another service to fork from. This has effect only when a new service is being created.

Name of another project to fork a service from. This has effect only when a new service is being created.

Dragonfly persistence

When persistence is 'rdb' or 'dfs', Dragonfly does RDB or DFS dumps every 10 minutes. Dumps are done according to the backup schedule for backup purposes. When persistence is 'off', no RDB/DFS dumps or backups are done, so data can be lost at any moment if the service is restarted for any reason, or if the service is powered off. Also, the service can't be forked.