Specific options when creating or updating a Redis™ service

You can find all the specific options for Redis™ by using the CLI help as such:

exo dbaas create --help-redis
  --redis-fork-from              name of a Database Service to fork from
  --redis-ip-filter              allow incoming connections from CIDR address block
  --redis-recovery-backup-name   the name of the backup to restore when forking from a Database Service
  --redis-settings               Redis configuration settings (JSON format)

Restricting connections from the Internet

By default, Exoscale DBaaS are accessible from 0.0.0.0/0 which is the whole Internet. Data does not transmit in clear over the network as it is SSL encrypted by default and authenticated.

To restrict the incoming connection to your database service, you can add a filter allowing:

  • just one IP address
  • a network range
  • a combination of the above

To do this update your service or create it with the ip filter which is a comma separated list of CIDRs exo dbaas update -z de-muc-1 test-redis --redis-ip-filter=1.2.3.4/24,5.6.7.8/32

Managing JSON configuration settings

You can list all settings available for the database service by using the command:

exo dbaas type show redis --settings redis

┼───────────────────────────────────┼───────────────┼────────────────────────────────────────────────────┼
│                KEY                │     TYPE      │                    DESCRIPTION                     │
┼───────────────────────────────────┼───────────────┼────────────────────────────────────────────────────┼
│ acl_channels_default              │ string        │ Determines default pub/sub channels' ACL for new   │
│                                   │               │ users if ACL is not supplied. When this option is  │
│                                   │               │ not defined, all_channels is assumed to keep       │
│                                   │               │ backward compatibility. This option doesn't affect │
│                                   │               │ Redis configuration acl-pubsub-default.            │
│                                   │               │   * Supported values:                              │
│                                   │               │     - allchannels                                  │
│                                   │               │     - resetchannels                                │
│ ssl                               │ boolean       │                                                    │
│ lfu_log_factor                    │ integer       │                                                    │
│ lfu_decay_time                    │ integer       │                                                    │
│ pubsub_client_output_buffer_limit │ integer       │ Set output buffer limit for pub / sub clients in   │
│                                   │               │ MB. The value is the hard limit, the soft limit is │
│                                   │               │ 1/4 of the hard limit. When setting the limit, be  │
│                                   │               │ mindful of the available memory in the selected    │
│                                   │               │ service plan.                                      │
│                                   │               │   * Minimum: 32 / Maximum: 512                     │
│                                   │               │   * Example: 64                                    │
│ timeout                           │ integer       │                                                    │
│ maxmemory_policy                  │ [string null] │                                                    │
│ io_threads                        │ integer       │                                                    │
│ notify_keyspace_events            │ string        │                                                    │
│ persistence                       │ string        │ When persistence is 'rdb', Redis does RDB dumps    │
│                                   │               │ each 10 minutes if any key is changed. Also RDB    │
│                                   │               │ dumps are done according to backup schedule for    │
│                                   │               │ backup purposes. When persistence is 'off', no RDB │
│                                   │               │ dumps and backups are done, so data can be lost at │
│                                   │               │ any moment if service is restarted for any reason, │
│                                   │               │ or if service is powered off. Also service can't   │
│                                   │               │ be forked.                                         │
│                                   │               │   * Supported values:                              │
│                                   │               │     - off                                          │
│                                   │               │     - rdb                                          │
┼───────────────────────────────────┼───────────────┼────────────────────────────────────────────────────┼

Refer to the equivalent section for Managed PostgreSQL