# Exoscale Documentation — Valkey > Managed Valkey: an open-source, in-memory key-value store and drop-in replacement for Redis®, for databases, caching or message brokers. --- url: https://community.exoscale.com/product/dbaas/service-specific/valkey/ --- # Valkey Valkey is an open-source, in-memory key-value store built for high performance, caching, message brokering, and real-time workloads. - [Quick Start - Valkey](https://community.exoscale.com/product/dbaas/service-specific/valkey/quick-start/index.md) - Get started quickly with a guided setup to achieve your first successful use of the service, including the required steps and configuration. - [Overview - Valkey](https://community.exoscale.com/product/dbaas/service-specific/valkey/overview/index.md) - Terminology and key features at a glance, learn the core concepts, capabilities, and options of this service before you dive deeper. - [How-To - Valkey](https://community.exoscale.com/product/dbaas/service-specific/valkey/how-to/index.md) - Step-by-step guides to configure the service and use specific features, with clear instructions for common tasks and problem solving. - [Service Boundaries - Valkey](https://community.exoscale.com/product/dbaas/service-specific/valkey/service-boundaries/index.md) - Service boundaries: quotas, limits, and the guaranteed service levels (SLA) for this product, including key constraints to plan and operate reliably. - [Reference - Valkey](https://community.exoscale.com/product/dbaas/service-specific/valkey/reference/index.md) - Reference documentation for API, CLI, and tools, browse comprehensive details, parameters, commands, and integration notes. --- url: https://community.exoscale.com/product/dbaas/service-specific/valkey/quick-start/ --- # Quick Start - Valkey ## Specific Options for Valkey You can find all the specific options for Valkey by using the CLI help: ```bash exo dbaas create --help-valkey --valkey-fork-from name of a Database Service to fork from --valkey-ip-filter allow incoming connections from CIDR address block --valkey-migration-dbname database name for bootstrapping the initial connection --valkey-migration-host hostname or IP address of the source server where to migrate data from --valkey-migration-ignore-dbs list of databases which should be ignored during migration --valkey-migration-method migration method to be used ("dump" or "replication") --valkey-migration-password password for authenticating to the source server --valkey-migration-port port number of the source server where to migrate data from --valkey-migration-ssl connect to the source server using SSL --valkey-migration-username username for authenticating to the source server --valkey-recovery-backup-name the name of the backup to restore when forking from a Database Service --valkey-settings Valkey configuration settings (JSON format) ``` --- url: https://community.exoscale.com/product/dbaas/service-specific/valkey/overview/ --- # Overview - Valkey Exoscale's Managed Valkey is an open-source, in-memory key-value data store designed as a drop-in replacement for Redis®. It offers high performance for databases, caching, or message brokers, ensuring data stays within Europe and complies with GDPR regulations. ## Terminology Valkey Service : a managed deployment of the Valkey engine on Exoscale Plan : pre-sized bundle of CPU, RAM & storage (Hobbyist, Startup, Business, Premium) Replica : follower node receiving asynchronous replication from the primary Fork : on-demand clone of an existing service, useful for tests or disaster recovery Eviction Policy : strategy Valkey uses when memory is exhausted (e.g. `vallkeys-lru`) ## Features Managed Lifecycle : automated provisioning, rolling upgrades and in-place re-sizing High Availability : configurable replica count (Business & Premium plans) with automatic fail-over Backups : daily encrypted snapshots retained 7 days (Hobbyist/Startup) or 14 days (Business/Premium) Metrics & Logging : Prometheus endpoint and streaming logs to your preferred target TLS Everywhere : client connections encrypted by default; IP filtering for extra control Full Redis Command Set : because Valkey 7.2.4 is binary-compatible with Redis 7 > [!NOTE] > _Open-Source Continuity in a Nutshell_ (Redis ---> _Valkey_) Same API, new > governance under the Linux Foundation; no licence fees, no code gatekeeping. > Exoscale switched its “Redis®” DBaaS offering to Valkey to guarantee > long-term open-source freedom for customers. --- url: https://community.exoscale.com/product/dbaas/service-specific/valkey/how-to/ --- # How-To - Valkey Step-by-step guides to configure the service and use specific features, with clear instructions for common tasks and problem solving. - [Connect with Valkey CLI](https://community.exoscale.com/product/dbaas/service-specific/valkey/how-to/connect-valkey-cli/index.md) - Install valkey-cli and connect to your Valkey database from the terminal to run INFO, KEYS, and other Redis-compatible commands. - [Migrate to Valkey](https://community.exoscale.com/product/dbaas/service-specific/valkey/how-to/migrating-to-valkey/index.md) - Migrate Redis or Valkey databases to Exoscale Managed Valkey using replication or scan with supported prerequisites and TLS. - [Restrict Connections](https://community.exoscale.com/product/dbaas/service-specific/valkey/how-to/restricting-connections/index.md) - Control Valkey access with IP filters using single addresses, CIDR ranges, or both to limit incoming database connections. - [Upgrade to Valkey](https://community.exoscale.com/product/dbaas/service-specific/valkey/how-to/upgrading-to-valkey/index.md) - Upgrade your service to Valkey from the portal using the service detail menu and the dedicated upgrade action. --- url: https://community.exoscale.com/product/dbaas/service-specific/valkey/how-to/connect-valkey-cli/ --- # Connect with Valkey CLI To connect to the Valkey database, you will need to install the [`valkey-cli` client](https://valkey.io/topics/cli/). Execute the following command from a terminal window: ```bash valkey-cli -u VALKEY_URI ``` To check the connection is working, execute the following command returning all Redis parameters: ```bash INFO ``` You can also list the keys using the command: ```bash KEYS * ``` --- url: https://community.exoscale.com/product/dbaas/service-specific/valkey/how-to/migrating-to-valkey/ --- # Migrate to Valkey > [!WARNING] > Due to the fact that migrations always involve interaction with third-party services running outside of Exoscale, > only best-effort support is provided on all migrations. Migrate your Redis® or Valkey server database to our Exoscale Managed Valkey service. There are two methods: - the **replication method** - the **scan method** The migration first attempts to use the replication method. If the replication method fails, it uses the scan method. The replication method is preferred for production databases because it allows for the migration of data with minimal downtime. The scan method is slower and iterates over all keys, one database at a time. ### Prerequisites - A target Redis service - a new or an existing service. - The hostname, port and password of the source Redis service. - The source Redis service must be secured with SSL/TLS, which is the default for migration. Refer to [Redis TLS support](https://redis.io/docs/latest/operate/oss_and_stack/management/security/) - A publicly accessible source Redis service (you might need to set a bind parameter to a publicly reachable network interface in your Redis configuration file). Any firewalls need to be open on port TCP 6379 if using the default to allow traffic from the source to the target servers. Also pay attention to other protections that can restrict connections: SELinux should be disabled or set in permissive mode for the duration of the migration on the source server. - The number of Redis databases from source to target needs to match. Use the command `redis-cli config get databases`. By default, Redis has 16 databases. If you are migrating more databases, adjust accordingly on the target with the command in the section below and create the target service first before migration. --- url: https://community.exoscale.com/product/dbaas/service-specific/valkey/how-to/restricting-connections/ --- # Restrict Connections By default, Exoscale DBaaS are not accessible from the whole internet. Data does not transmit in clear over the network as it is SSL encrypted by default and authenticated. To allow incoming connections to your database service, you can add a filter allowing: - just one IP address, - a network range, - or a combination of IP address and network range To do this, update your service or create it with the IP filter, which is a comma separated list of CIDRs. --- url: https://community.exoscale.com/product/dbaas/service-specific/valkey/how-to/upgrading-to-valkey/ --- # Upgrade to Valkey Migration is possible via a specific operation available in the web portal, from top right menu in the service detail view. ![](dbaas-upgrade-to-valkey.png "Upgrade to Valkey button") --- url: https://community.exoscale.com/product/dbaas/service-specific/valkey/service-boundaries/ --- # Service Boundaries - Valkey - [Limits and Quotas - Valkey](https://community.exoscale.com/product/dbaas/service-specific/valkey/service-boundaries/limits-and-quotas/index.md) - Managed Valkey Limitations and Quotas - [SLA - Valkey](https://community.exoscale.com/product/dbaas/service-specific/valkey/service-boundaries/sla/index.md) - Managed Valkey Service Level Agreement - [Pricing ↗︎](https://www.exoscale.com/pricing/#managed-valkey) --- url: https://community.exoscale.com/product/dbaas/service-specific/valkey/service-boundaries/limits-and-quotas/ --- # Limits and Quotas - Valkey ## Limits - Migration wizard is **not yet available**; use `redis-cli --rdb` or `replication` to move data - Multi-primary (Redis Cluster-style sharding) is **not supported**; scale is vertical + read replicas - Functionality is limited to core Valkey; no Redis Stack or proprietary modules - Portal currently exposes basic operations only; use **CLI/API** for advanced settings Service Plans Restrictions : Access to certain plans (e.g., Business, Premium) requires activation by the support team. Requests can be made during service creation. ## Quotas | Usage | Quota | | -------------------------------------------------------- | ------------------------ | | DBaaS services overall | 10 | ## Availability Managed Valkey is available in all zones. --- url: https://community.exoscale.com/product/dbaas/service-specific/valkey/service-boundaries/sla/ --- # SLA - Valkey Refere to the overall [DBaaS SLA](https://community.exoscale.com/product/dbaas/service-boundaries/sla/index.md). --- url: https://community.exoscale.com/product/dbaas/service-specific/valkey/reference/ --- # Reference - Valkey - [API DBaaS](https://community.exoscale.com/reference/api/dbaas/dbaas-valkey/index.md) - All operations on DBaaS. (external) - [CLI DBaaS](https://community.exoscale.com/reference/cli/exo/dbaas/index.md) - All commands on DBaaS. (external)