Key-Value Store (Redis Compatible)
On-Demand Key-Value Store instances can be managed with our command-line tool nctl or by directly using the Nine Self Service API.
Billing is automated based on the resources used. Nine's automated management ensures the smooth operation of the service.
On-Demand Key-Value Stores offer limited configuration options. If more extensive settings are required, use our Key-Value Stores as a Managed Service.
Version
Currently, the latest version 7 of Redis is being used to power On-Demand Key-Value Stores. Due to licence changes and the associated uncertainty about the future development of Redis, we have decided to use a Redis-compatible alternative as a replacement in the near future.
Pricing
| nine-key-value-store-1gb | nine-key-value-store-2gb | nine-key-value-store-4gb | x gb | |
|---|---|---|---|---|
| RAM | 1 GB | 2 GB | 4 GB | x GB |
| Storage space | 2 GB | 4 GB | 8 GB | x * 2 GB |
| Monthly fees | x * |
Pricing for On-Demand Key-Value Stores start at . Additional charges are based on the resources used.
Configuration options
On-Demand Services come with a sensible base configuration that is suitable for most setups. They also provide the ability to change certain configuration options. Adjusting these configuration options can result in a restart of the instance.
The instance can be customized with the following configuration options:
Name
The name of the instance can be freely chosen, but must be unique. Once created, the name cannot be changed.
Location
Depending on available resources, instances can be created in two locations within the "ColoZüri" data center or the "NTT" data center in Rümlang. The location cannot be changed later.
Allowed IP addresses
IPv4 addresses and address ranges from which connections to the service can be established. Access from our Kubernetes products NKE and GKE as well as from deplo.io is already enabled.
The access restriction can be adjusted at any time. Adjustments are made non-disruptively moments after the form is submitted.
maxmemory Policy
The configuration option maxmemory_policy defines what should happen when the available memory is exhausted.
By default, the policy allkeys-lru is used, which keeps the most recently used keys and removes the least recently used (LRU) keys.
An overview of all policies can be found in the Redis documentation.
Connecting
The connection information (FQDN and TOKEN) for an instance can be found in Cockpit under Access Information as well as the output of nctl. Use nctl get kvs to display the FQDN and the --print-token parameter for the token. The instances are accessible via the standard Redis port 6379.
The instance will only accept TLS connections. Depending on the client or library, you may need to explicitly enable TLS.
As per Allowed IP Addresses, you may need to allow additional IP's to connect to your instance.
- Cockpit
- nctl
REDISCLI_AUTH='TOKEN' redis-cli --tls --insecure -h FQDN
nctl get kvs # note the NAME and FQDN of your instance
nctl update kvs NAME --allowed-cidrs=203.0.113.1/32 # replace NAME and 203.0.113.1 with your public IP address to allow connections from your system
export REDISCLI_AUTH=$(nctl get kvs NAME --print-token) # replace NAME to configure the password as ENV variable
redis-cli --tls --insecure -h FQDN # replace FQDN to connect to the correct endpoint
Users
A user "default" with a password is created for connection authentication when the instance is created. Since "default" is the standard user, only the password is required when connecting.
Backups
Stored keys and values are persisted across instance restarts, but no restorable backups are created.