diff --git a/changelog/august2023/2023-08-21-redistm-changed-default-username-is-now.mdx b/changelog/august2023/2023-08-21-redistm-changed-default-username-is-now.mdx index 20c852866e..327f0b2d37 100644 --- a/changelog/august2023/2023-08-21-redistm-changed-default-username-is-now.mdx +++ b/changelog/august2023/2023-08-21-redistm-changed-default-username-is-now.mdx @@ -6,7 +6,7 @@ author: url: 'https://slack.scaleway.com' date: 2023-08-21 category: databases -product: redistm +product: redis --- You can now use the `default` username on your managed database for Redis. This enables some software integrations where specific usernames are not supported. Anonymous connection remains unavailable. diff --git "a/changelog/databases/january2023/2023-01-06-redistm-added-managed-database-for-redis\342\204\242.mdx" "b/changelog/databases/january2023/2023-01-06-redistm-added-managed-database-for-redis\342\204\242.mdx" index ce82e16cef..7dde29b537 100644 --- "a/changelog/databases/january2023/2023-01-06-redistm-added-managed-database-for-redis\342\204\242.mdx" +++ "b/changelog/databases/january2023/2023-01-06-redistm-added-managed-database-for-redis\342\204\242.mdx" @@ -1,13 +1,13 @@ --- -title: Managed Database for Redis™ has a new Availabilty Zone! +title: Managed Database for Redis® has a new Availabilty Zone! status: added author: fullname: 'Join the #managed-database-for-redis channel on Slack.' url: 'https://slack.scaleway.com' date: 2023-01-06 category: databases -product: redistm +product: redis --- -Managed Database for Redis™ is now available in the Availability Zone `pl-waw-2`! +Managed Database for Redis® is now available in the Availability Zone `pl-waw-2`! diff --git a/changelog/databases/july2022/2022-07-26-redis-added-redis-ga.mdx b/changelog/databases/july2022/2022-07-26-redis-added-redis-ga.mdx index 207b18d0e0..f2d5aac86c 100644 --- a/changelog/databases/july2022/2022-07-26-redis-added-redis-ga.mdx +++ b/changelog/databases/july2022/2022-07-26-redis-added-redis-ga.mdx @@ -1,15 +1,15 @@ --- -title: Databases for Redis™ is in public beta +title: Databases for Redis® is in public beta status: added author: fullname: 'Join the #database channel on Slack.' url: 'https://slack.scaleway.com/' date: 2022-07-26 category: databases -product: redistm +product: redis --- -Databases for Redis™ is now available in Public Beta in the following Availability Zones: +Databases for Redis® is now available in Public Beta in the following Availability Zones: * `fr-par-1` * `fr-par-2` * `nl-ams-1` diff --git a/changelog/databases/november2022/2022-11-10-redis-new-availability-zone.mdx b/changelog/databases/november2022/2022-11-10-redis-new-availability-zone.mdx index e19da12a4b..502b6f5c26 100644 --- a/changelog/databases/november2022/2022-11-10-redis-new-availability-zone.mdx +++ b/changelog/databases/november2022/2022-11-10-redis-new-availability-zone.mdx @@ -1,13 +1,13 @@ --- -title: Managed Database for Redis™ has a new Availability Zone! +title: Managed Database for Redis® has a new Availability Zone! status: added author: fullname: 'Join the #database channel on Slack.' url: 'https://slack.scaleway.com/' date: 2022-11-08 category: databases -product: redistm +product: redis --- -[Managed Database for Redis™](/managed-databases/redis/quickstart/) is now available in the Availability Zone `nl-ams-2`! +[Managed Database for Redis®](/managed-databases/redis/quickstart/) is now available in the Availability Zone `nl-ams-2`! diff --git a/changelog/databases/october2022/2022-10-06-redis-ga-changed.mdx b/changelog/databases/october2022/2022-10-06-redis-ga-changed.mdx index 081877cef8..507ce33e63 100644 --- a/changelog/databases/october2022/2022-10-06-redis-ga-changed.mdx +++ b/changelog/databases/october2022/2022-10-06-redis-ga-changed.mdx @@ -1,15 +1,15 @@ --- -title: Managed Database for Redis™ is in General Availability +title: Managed Database for Redis® is in General Availability status: changed author: fullname: 'Join the #database channel on Slack.' url: 'https://slack.scaleway.com/' date: 2022-10-06 category: databases -product: redistm +product: redis --- -[Managed Database for Redis™](/managed-databases/redis/how-to/create-a-database-for-redis/) is now in General Availability in the following Availability Zones: +[Managed Database for Redis®](/managed-databases/redis/how-to/create-a-database-for-redis/) is now in General Availability in the following Availability Zones: * `fr-par-1` * `fr-par-2` * `nl-ams-1` diff --git a/changelog/september2024/2024-09-13-redistm-added-new-redis-metrics-in-cockpit.mdx b/changelog/september2024/2024-09-13-redistm-added-new-redis-metrics-in-cockpit.mdx index bf4ac1b285..e04f8420f1 100644 --- a/changelog/september2024/2024-09-13-redistm-added-new-redis-metrics-in-cockpit.mdx +++ b/changelog/september2024/2024-09-13-redistm-added-new-redis-metrics-in-cockpit.mdx @@ -1,12 +1,12 @@ --- -title: New Redis™ metrics in Cockpit +title: New Redis® metrics in Cockpit status: added author: fullname: 'Join the #database channel on Slack.' url: 'https://slack.scaleway.com' date: 2024-09-13 category: databases -product: redistm +product: redis --- New Redis metrics are available in Cockpit: diff --git a/console/account/how-to/use-the-search-bar.mdx b/console/account/how-to/use-the-search-bar.mdx index 4c178b7719..8b0d2f2752 100644 --- a/console/account/how-to/use-the-search-bar.mdx +++ b/console/account/how-to/use-the-search-bar.mdx @@ -51,8 +51,8 @@ In addition to the products present in the Scaleway catalog, you can look for th - Block Storage snapshots - PostgreSQL snapshots - PostgreSQL backups -- Redis™ Database Instances -- Redis™ clusters +- Redis® Database Instances +- Redis® clusters - VPC - VPC Private Networks - Public Gateways diff --git a/console/account/reference-content/products-availability.mdx b/console/account/reference-content/products-availability.mdx index d736a473c2..ae6b236d77 100644 --- a/console/account/reference-content/products-availability.mdx +++ b/console/account/reference-content/products-availability.mdx @@ -38,7 +38,7 @@ Scaleway products are available in multiple regions and locations worldwide. Thi | | Object Storage Glacier | Paris* | Not available yet | Not available yet | | | Block Storage | PAR1, PAR2, PAR3 | AMS1, AMS2, AMS3 | WAW1, WAW2, WAW3 | | **Managed Databases** | PostgreSQL - MySQL | Across Paris region | Across Amsterdam region | Across Warsaw region | -| | Redis™ | PAR1, PAR2 | AMS1, AMS2 | WAW1 | +| | Redis® | PAR1, PAR2 | AMS1, AMS2 | WAW1 | | **Network** | Private Networks | Across Paris region | Across Amsterdam region | Across Warsaw region | | | Public Gateway | PAR1, PAR2, PAR3 | AMS1, AMS2, AMS3 | WAW1, WAW2, WAW3 | | | Load Balancer | PAR1, PAR2, PAR3 | AMS1, AMS2, AMS3 | WAW1, WAW2, WAW3 | diff --git a/faq/databases-for-redis.mdx b/faq/databases-for-redis.mdx index 6279b88212..cb3e76faef 100644 --- a/faq/databases-for-redis.mdx +++ b/faq/databases-for-redis.mdx @@ -1,62 +1,62 @@ --- meta: - title: Managed Database for Redis™ FAQ - description: Discover Scaleway Managed Databases and how to access it for Redis™. + title: Managed Database for Redis® FAQ + description: Discover Scaleway Managed Databases and how to access it for Redis®. content: - h1: Managed Database for Redis™ + h1: Managed Database for Redis® hero: assets/database-redis.webp dates: validation: 2024-08-05 category: managed-databases --- -## What is Scaleway Managed Database for Redis™ +## What is Scaleway Managed Database for Redis® -Managed Database for Redis™* is a low-latency caching solution. It allows you to easily set up a secure cache and lighten the load on your main database. -Based on the in-memory data storage, Managed Database for Redis™ improves your application response time and helps you provide a better experience to your users. -Using Managed Database for Redis™ as a cache optimizes the speed of your requests as copies of the most frequently used data are stored in memory, making them accessible in milliseconds. [Learn more about Managed Database for Redis™](/managed-databases/redis/how-to/create-a-database-for-redis/). +Managed Database for Redis®* is a low-latency caching solution. It allows you to easily set up a secure cache and lighten the load on your main database. +Based on the in-memory data storage, Managed Database for Redis® improves your application response time and helps you provide a better experience to your users. +Using Managed Database for Redis® as a cache optimizes the speed of your requests as copies of the most frequently used data are stored in memory, making them accessible in milliseconds. [Learn more about Managed Database for Redis®](/managed-databases/redis/how-to/create-a-database-for-redis/). ## Why is it ideal for Cache usage? -Based on the **Re**mote **Di**ctionary **S**erver technology, Scaleway Managed Database for Redis™ stores your data in the RAM of the underlying machine rather than on a disk (SSD/HDD). +Based on the **Re**mote **Di**ctionary **S**erver technology, Scaleway Managed Database for Redis® stores your data in the RAM of the underlying machine rather than on a disk (SSD/HDD). In other words, for each request to read, insert, or update data in a database, this can be executed using data available in the fastest and closest storage of your compute resource, the memory. -Traditional databases like MySQL or PostgreSQL store data on a disk which inevitably introduces IOPs and results in latency on each operation. Redis™ is known for delivering millisecond response time and high performance for millions of requests per second to empower demanding workloads. -The combination of powerful in-memory data storage such as Redis™ and managing the resources set-up, securitization, scaling, and maintenance makes Scaleway Managed Database for Redis™ a handy solution to improve the usability of your application. -One of the most common ways to implement cache is storing frequently accessed data in Redis™ (therefore in memory) and serving your application's request. +Traditional databases like MySQL or PostgreSQL store data on a disk which inevitably introduces IOPs and results in latency on each operation. Redis® is known for delivering millisecond response time and high performance for millions of requests per second to empower demanding workloads. +The combination of powerful in-memory data storage such as Redis® and managing the resources set-up, securitization, scaling, and maintenance makes Scaleway Managed Database for Redis® a handy solution to improve the usability of your application. +One of the most common ways to implement cache is storing frequently accessed data in Redis® (therefore in memory) and serving your application's request. If data is unavailable in memory, it can always be retrieved from the primary database. Below is a simplified schema explaining this process. -## How can I access my Managed Database for Redis™ once it is provisioned? +## How can I access my Managed Database for Redis® once it is provisioned? -You can connect to your Managed Database for Redis™ using the IP address(es) and port(s) available on the details page of your Redis™ Database Instance next to the title **Endpoints**. +You can connect to your Managed Database for Redis® using the IP address(es) and port(s) available on the details page of your Redis® Database Instance next to the title **Endpoints**. - There are as many `IP:port` endpoints as nodes in your cluster (one if standalone). - If you are in cluster mode (3 nodes or more), you have to use a cluster-specific connector cable to connect to multiple endpoints. -## What is the Private Networks feature for Redis™ Database Instances? +## What is the Private Networks feature for Redis® Database Instances? -[Private Networks](/network/public-gateways/quickstart/) allow you to configure your Layer-2 network with IPv4 addresses on Managed Database for Redis™ Instances. +[Private Networks](/network/public-gateways/quickstart/) allow you to configure your Layer-2 network with IPv4 addresses on Managed Database for Redis® Instances. -It also increases the security of your databases since Instances in your Private Networks can directly be connected to your Redis™ Database Instance without passing through the public internet. -In standalone mode, you can attach Private Networks to your Redis™ Database Instances at the creation level or add a Private Networks endpoint to your existing Redis™ Database Instance from the console. +It also increases the security of your databases since Instances in your Private Networks can directly be connected to your Redis® Database Instance without passing through the public internet. +In standalone mode, you can attach Private Networks to your Redis® Database Instances at the creation level or add a Private Networks endpoint to your existing Redis® Database Instance from the console. - When you select cluster mode, Private Networks can only be selected and configured upon creating the Redis™ Database Instance. Once the cluster has been completed, it is impossible to attach it to a Private Network or to edit the configuration of an existing one. If you want to switch to a public network or update your IP addresses, you must create a new Redis™ Database Instance. + When you select cluster mode, Private Networks can only be selected and configured upon creating the Redis® Database Instance. Once the cluster has been completed, it is impossible to attach it to a Private Network or to edit the configuration of an existing one. If you want to switch to a public network or update your IP addresses, you must create a new Redis® Database Instance. ## How many Private Networks can I attach? -Currently, you can connect one Private Network to each Redis™ Database Instance in the Scaleway console. For standalone Instances, you can attach multiple Private Networks via the CLI or the API only. +Currently, you can connect one Private Network to each Redis® Database Instance in the Scaleway console. For standalone Instances, you can attach multiple Private Networks via the CLI or the API only. ## Can I use any IP Range for my Private Network? -For now, only the [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918) IP subnets are accepted as a Redis™ Database Instance virtual IPv4. +For now, only the [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918) IP subnets are accepted as a Redis® Database Instance virtual IPv4. -## How is the Redis™ Database's failover IP managed? +## How is the Redis® Database's failover IP managed? -The Redis™ controller knows the cluster topology and automatically routes requests to a healthy node. In case of unavailability of one of the cluster nodes, no downtime is to be expected. +The Redis® controller knows the cluster topology and automatically routes requests to a healthy node. In case of unavailability of one of the cluster nodes, no downtime is to be expected. ## What should I use as virtual IP? How do I calculate the CIDR netmask? @@ -66,7 +66,7 @@ In a cluster topology, you must [provide a private IPv4 address](/faq/databases- A Redis cluster contains a minimum of 3 nodes and up to 6 nodes. Each node contains a source and a replica. The cluster nodes use hash partitioning to split the keyspace into 16,384 key slots. Each source of the cluster is responsible for a subset of those slots. -Each replica copies the data of one of the sources. For example, on a three-node Redis™ Database Instance cluster, three Instances host each a source and a replica of one of the other nodes' sources. +Each replica copies the data of one of the sources. For example, on a three-node Redis® Database Instance cluster, three Instances host each a source and a replica of one of the other nodes' sources. If one of the sources fails, the remaining nodes hold a vote and elect the replica that will be promoted as the new source. When the failing source rejoins the cluster, it automatically becomes a replica. It begins to copy the data of the source of another node. @@ -78,7 +78,7 @@ You can scale your cluster horizontally up to six nodes. Below is an example of Each of the three Instances acts as a primary node and replicates one of the others as a secondary node. -## What are the differences between Redis™ node classes? +## What are the differences between Redis® node classes? Two node classes are available for Managed Database for Redis: **Development** and **Production**. @@ -96,9 +96,9 @@ This is much better for scaling as the operation is spread across multiple nodes -A two-node architecture for Redis™ with a primary node being duplicated in a standby node might increase the durability of the data but does not prevent the service from failing as automatic failover is not available for Redis databases. +A two-node architecture for Redis® with a primary node being duplicated in a standby node might increase the durability of the data but does not prevent the service from failing as automatic failover is not available for Redis databases. This means that the primary node will be a Single Point Of failure. -Scaleway does not provide two nodes HA Redis™ Database Instances but offers a state-of-the-art Redis Cluster Architecture, which can scale vertically and horizontally with built-in High Availability. +Scaleway does not provide two nodes HA Redis® Database Instances but offers a state-of-the-art Redis Cluster Architecture, which can scale vertically and horizontally with built-in High Availability. ## Can I change the username and password of my Database Instance's default user? diff --git a/identity-and-access-management/iam/reference-content/permission-sets.mdx b/identity-and-access-management/iam/reference-content/permission-sets.mdx index e602197404..c1d886ccb0 100644 --- a/identity-and-access-management/iam/reference-content/permission-sets.mdx +++ b/identity-and-access-management/iam/reference-content/permission-sets.mdx @@ -75,8 +75,8 @@ Below is a list of the permission sets available at Scaleway. | ObjectStorageObjectsDelete | Access to delete objects | | ObjectStorageBucketsWrite | Access to create and edit buckets, bucket configuration including lifecycle rules | | ObjectStorageBucketsDelete | Access to delete buckets | -| RedisReadOnly | List and read access to Managed Database for Redis™ | -| RedisFullAccess | Full access to create, read, list, edit and delete Managed Database for Redis™ | +| redisreadOnly | List and read access to Managed Database for Redis® | +| RedisFullAccess | Full access to create, read, list, edit and delete Managed Database for Redis® | | PrivateNetworksFullAccess | Full access to create, read, list, edit and delete Private Networks | | VPCGatewayReadOnly | List and read access to Public Gateways | | VPCGatewayFullAccess | Full access to create, read, list, edit and delete Public Gateways | diff --git a/managed-databases/postgresql-and-mysql/index.mdx b/managed-databases/postgresql-and-mysql/index.mdx index eca866f682..7fe93a782a 100644 --- a/managed-databases/postgresql-and-mysql/index.mdx +++ b/managed-databases/postgresql-and-mysql/index.mdx @@ -65,7 +65,7 @@ meta: label="Read more" /> diff --git a/managed-databases/redis/api-cli/index.mdx b/managed-databases/redis/api-cli/index.mdx index c3b5fc6954..ec182d2648 100644 --- a/managed-databases/redis/api-cli/index.mdx +++ b/managed-databases/redis/api-cli/index.mdx @@ -1,8 +1,8 @@ --- meta: - title: Managed Database for Redis™ - API/CLI - description: Managed Database for Redis™ API/CLI Documentation + title: Managed Database for Redis® - API/CLI + description: Managed Database for Redis® API/CLI Documentation content: - h1: Managed Database for Redis™ - API/CLI - paragraph: Managed Database for Redis™ API/CLI Documentation + h1: Managed Database for Redis® - API/CLI + paragraph: Managed Database for Redis® API/CLI Documentation --- diff --git a/managed-databases/redis/api-cli/managing-username-and-password.mdx b/managed-databases/redis/api-cli/managing-username-and-password.mdx index 52bd89a5b1..abc6e047fd 100644 --- a/managed-databases/redis/api-cli/managing-username-and-password.mdx +++ b/managed-databases/redis/api-cli/managing-username-and-password.mdx @@ -1,10 +1,10 @@ --- meta: title: Managing the default user's username and password - description: Learn to manage Redis™ usernames and passwords using API/CLI. + description: Learn to manage Redis® usernames and passwords using API/CLI. content: h1: Managing the default user's username and password - paragraph: Learn to manage Redis™ usernames and passwords using API/CLI. + paragraph: Learn to manage Redis® usernames and passwords using API/CLI. tags: databases user redis username password dates: validation: 2024-04-08 @@ -13,7 +13,7 @@ categories: - redis --- -When you create a Redis™* Database Instance, you have to specify a user. It will be created with [set permissions](/managed-databases/redis/reference-content/default-user-permissions/). +When you create a Redis®* Database Instance, you have to specify a user. It will be created with [set permissions](/managed-databases/redis/reference-content/default-user-permissions/). You can specify a name for this user when you create a Database Instance. This allows you to ensure the username is compatible with different software integrations where specific usernames are not supported. @@ -30,7 +30,7 @@ You can specify a name for this user when you create a Database Instance. This a Follow the [create a Database Instance](https://www.scaleway.com/en/developers/api/managed-database-redis/#quickstart) procedure. -You can also define a username when you [create a Redis™ Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) via the Scaleway console. +You can also define a username when you [create a Redis® Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) via the Scaleway console. You are required to specify a username and password for the default user in your POST request payload. @@ -51,7 +51,7 @@ You can retrieve the default username via the API and the CLI. - Run the following curl command in a terminal to `GET` information about your Redis™ Database Instance of choice and retrieve the default username. Replace `zone` and `cluster_id` in the path with the zone and cluster ID of your Database Instance of choice. + Run the following curl command in a terminal to `GET` information about your Redis® Database Instance of choice and retrieve the default username. Replace `zone` and `cluster_id` in the path with the zone and cluster ID of your Database Instance of choice. ```bash curl -X GET \ @@ -62,7 +62,7 @@ You can retrieve the default username via the API and the CLI. - Run the following command in a terminal to `GET` information about your Redis™ Database Instance. Replace `` with the ID of your Database Instance of choice. + Run the following command in a terminal to `GET` information about your Redis® Database Instance. Replace `` with the ID of your Database Instance of choice. ```bash scw redis cluster get @@ -107,7 +107,7 @@ You can change the username and password of the default user anytime via the API - Run the following curl command in a terminal to update your Redis™ Database Instance. Replace `zone` and `cluster_id` in the path with the zone and cluster ID of your Database Instance of choice. In the body of the request, replace `` and `` with your username and password of choice. + Run the following curl command in a terminal to update your Redis® Database Instance. Replace `zone` and `cluster_id` in the path with the zone and cluster ID of your Database Instance of choice. In the body of the request, replace `` and `` with your username and password of choice. ```bash curl -X PATCH \ @@ -125,7 +125,7 @@ You can change the username and password of the default user anytime via the API - Run the following command in a terminal to `GET` information about your Redis™ Database Instance. Replace `` with the ID of your Database Instance of choice. Replace `` with your Database Instance ID, and `` and `` with your username and password of choice. + Run the following command in a terminal to `GET` information about your Redis® Database Instance. Replace `` with the ID of your Database Instance of choice. Replace `` with your Database Instance ID, and `` and `` with your username and password of choice. ```bash scw redis cluster update user-name="" password="" diff --git a/managed-databases/redis/api-cli/using-pub-sub-feature.mdx b/managed-databases/redis/api-cli/using-pub-sub-feature.mdx index 609d60af0c..28c2589934 100644 --- a/managed-databases/redis/api-cli/using-pub-sub-feature.mdx +++ b/managed-databases/redis/api-cli/using-pub-sub-feature.mdx @@ -1,10 +1,10 @@ --- meta: - title: Using Publish/Subscribe messaging with Redis™ - description: Guide to using the Pub/Sub feature in Redis™ with API/CLI. + title: Using Publish/Subscribe messaging with Redis® + description: Guide to using the Pub/Sub feature in Redis® with API/CLI. content: - h1: Using Publish/Subscribe messaging with Redis™ - paragraph: Guide to using the Pub/Sub feature in Redis™ with API/CLI. + h1: Using Publish/Subscribe messaging with Redis® + paragraph: Guide to using the Pub/Sub feature in Redis® with API/CLI. tags: databases redis pub/sub messaging broker dates: validation: 2024-04-15 @@ -13,7 +13,7 @@ categories: - redis --- -The Publish/Subscribe feature is available with Redis™* 6 and 7. +The Publish/Subscribe feature is available with Redis®* 6 and 7. Pub/Sub is a highly scalable messaging model fit to handle large amounts of data and that enables asynchronous communication on low bandwidth. @@ -27,9 +27,9 @@ To implement Pub/Sub using Redis, you can run commands such as `PUBLISH` and `SU - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Redis™ Database Instance](/managed-databases/redis/quickstart/) with Redis™ version 6 or 7 +- A [Redis® Database Instance](/managed-databases/redis/quickstart/) with Redis® version 6 or 7 -1. [Connect to your Redis™ Database Instance](/managed-databases/redis/how-to/connect-to-redis-database-instance/). +1. [Connect to your Redis® Database Instance](/managed-databases/redis/how-to/connect-to-redis-database-instance/). 2. Subscribe to a topic. In this tutorial, we will use `temperature` as an example of topic. ``` > SUBSCRIBE temperature @@ -38,7 +38,7 @@ To implement Pub/Sub using Redis, you can run commands such as `PUBLISH` and `SU 2) "myqueue" 3) (integer) 1 ``` -3. Publish to the topic in a separate client. You can connect to the same Redis™ Database Instance in a different terminal to do so. +3. Publish to the topic in a separate client. You can connect to the same Redis® Database Instance in a different terminal to do so. ``` > PUBLISH temperature monday/12C (integer) 1 diff --git a/managed-databases/redis/concepts.mdx b/managed-databases/redis/concepts.mdx index b4b8b1341b..c67b9fb097 100644 --- a/managed-databases/redis/concepts.mdx +++ b/managed-databases/redis/concepts.mdx @@ -1,10 +1,10 @@ --- meta: - title: Managed Database for Redis™ - Concepts - description: Understand the key concepts behind Scaleway Managed Databases for Redis™. + title: Managed Database for Redis® - Concepts + description: Understand the key concepts behind Scaleway Managed Databases for Redis®. content: - h1: Managed Database for Redis™ - Concepts - paragraph: This page explains all the concepts related to Managed Database for Redis™. + h1: Managed Database for Redis® - Concepts + paragraph: This page explains all the concepts related to Managed Database for Redis®. tags: endpoint redis allowed-ip cluster cluster-mode availability horizontal-scaling tcp tls vertical-scaling dates: validation: 2024-04-15 @@ -19,11 +19,11 @@ Access control list (ACL) rules [define permissions for remote access to a Datab ## Cluster -A Redis™* cluster consists of a set of primary and secondary nodes. The cluster nodes use hash partitioning to split the keyspace into 16,384 key slots. Each primary of the cluster is responsible for a subset of those slots. Each secondary node replicates the data of one of the primary ones. +A Redis®* cluster consists of a set of primary and secondary nodes. The cluster nodes use hash partitioning to split the keyspace into 16,384 key slots. Each primary of the cluster is responsible for a subset of those slots. Each secondary node replicates the data of one of the primary ones. ## Cluster mode -Each Managed Database for Redis™ cluster consists of minimum three and maximum six compute Instances hosting each a primary Redis™ Instance and a secondary Instance for one of the other nodes. If one of the primary nodes fails, the remaining nodes hold a vote and elect one of the remaining secondary nodes as the new primary node. When the failing node rejoins the cluster, it automatically becomes a secondary node and begins to replicate the data of another primary node. +Each Managed Database for Redis® cluster consists of minimum three and maximum six compute Instances hosting each a primary Redis® Instance and a secondary Instance for one of the other nodes. If one of the primary nodes fails, the remaining nodes hold a vote and elect one of the remaining secondary nodes as the new primary node. When the failing node rejoins the cluster, it automatically becomes a secondary node and begins to replicate the data of another primary node. ## Endpoint @@ -35,11 +35,11 @@ A Database Instance is made up of multiple (at least 1) dedicated compute nodes, ## High availability -High Availability is handled through the Redis™ clustering feature. This is a 3-node multi-master architecture. In case of downtime on a node in the cluster, a new node is able to take over the requests with minimal downtime. +High Availability is handled through the Redis® clustering feature. This is a 3-node multi-master architecture. In case of downtime on a node in the cluster, a new node is able to take over the requests with minimal downtime. ## Horizontal scaling -A feature that allows you to increase the size of your Redis™ Database Instance infrastructure by adding more nodes to your Database Instance to increase your number of endpoints and distribute cache. +A feature that allows you to increase the size of your Redis® Database Instance infrastructure by adding more nodes to your Database Instance to increase your number of endpoints and distribute cache. ## In-memory database @@ -51,7 +51,7 @@ Compared to traditional database management, which requires customers to provisi ## Max memory -A configuration directive used to set the maximum amount of memory Redis™ can use for a data set. You can set this value via the Scaleway console or by configuring the `available_settings` via API. +A configuration directive used to set the maximum amount of memory Redis® can use for a data set. You can set this value via the Scaleway console or by configuring the `available_settings` via API. ## Region and Availability Zone @@ -67,7 +67,7 @@ Transport Layer Security (TLS) is an internet security protocol that enables dat ## Vertical scaling -Feature that allows you to increase the size of your Redis™ Database Instance by upgrading to a bigger node type to allow increased traffic for the same endpoint. +Feature that allows you to increase the size of your Redis® Database Instance by upgrading to a bigger node type to allow increased traffic for the same endpoint.
* Redis is a trademark of Redis Labs Ltd. Any rights therein are reserved to Redis Labs Ltd. Any use by Scaleway is for referential purposes only and does not indicate any sponsorship, endorsement or affiliation between Redis and Scaleway. \ No newline at end of file diff --git a/managed-databases/redis/how-to/configure-advanced-settings-redis.mdx b/managed-databases/redis/how-to/configure-advanced-settings-redis.mdx index 934a96251e..2c6e264bf7 100644 --- a/managed-databases/redis/how-to/configure-advanced-settings-redis.mdx +++ b/managed-databases/redis/how-to/configure-advanced-settings-redis.mdx @@ -1,10 +1,10 @@ --- meta: title: How to configure advanced settings - description: Guide to configuring advanced settings for your Redis™ database. + description: Guide to configuring advanced settings for your Redis® database. content: h1: How to configure advanced settings - paragraph: Guide to configuring advanced settings for your Redis™ database. + paragraph: Guide to configuring advanced settings for your Redis® database. tags: managed-database advanced-settings advanced setting dates: validation: 2024-07-04 @@ -14,29 +14,29 @@ categories: - postgresql-and-mysql --- -Advanced settings allow you to modify the default configuration of your Redis™* Database Instances. +Advanced settings allow you to modify the default configuration of your Redis®* Database Instances. - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Redis™ Database Instance](/managed-databases/redis/quickstart/) +- A [Redis® Database Instance](/managed-databases/redis/quickstart/) Changing the advanced settings can have an impact on the performance of your Database Instance. -1. Click **Redis™** under **Managed Databases** on the side menu. A list of your Database Instances displays. +1. Click **Redis®** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the database name or > **More info** to access the Database Instance information page. 3. Click the **Advanced settings** tab. To add advanced settings, follow these steps: - Click **Add advanced settings**. - - Select a parameter from the drop-down list. For Redis™ Database Instances, you can configure: + - Select a parameter from the drop-down list. For Redis® Database Instances, you can configure: - `tcp-keepalive` - the period used to send Acknowledgment flags (ACKs), specified in seconds - `maxclients` - the maximum number of clients that can be connected at the same time - - `maxmemory-policy` - parameter that defines how Redis™ selects what data to remove when maximum memory is reached. + - `maxmemory-policy` - parameter that defines how Redis® selects what data to remove when maximum memory is reached. - Configure the value associated with your setting. - Click to validate. diff --git a/managed-databases/redis/how-to/connect-to-redis-database-instance.mdx b/managed-databases/redis/how-to/connect-to-redis-database-instance.mdx index c9a38c3a73..c6cbf73357 100644 --- a/managed-databases/redis/how-to/connect-to-redis-database-instance.mdx +++ b/managed-databases/redis/how-to/connect-to-redis-database-instance.mdx @@ -1,10 +1,10 @@ --- meta: - title: How to connect to a Redis™ Database Instance - description: Instructions for connecting to your Scaleway Redis™ Database Instance. + title: How to connect to a Redis® Database Instance + description: Instructions for connecting to your Scaleway Redis® Database Instance. content: - h1: How to connect to a Redis™ Database Instance - paragraph: Instructions for connecting to your Scaleway Redis™ Database Instance. + h1: How to connect to a Redis® Database Instance + paragraph: Instructions for connecting to your Scaleway Redis® Database Instance. tags: postgresql mysql database-instance managed-database database dates: validation: 2024-07-04 @@ -14,29 +14,29 @@ categories: - redis --- -You can connect to your Redis™* Database Instance using the [Redis™ CLI](https://redis.io/docs/ui/cli/). +You can connect to your Redis®* Database Instance using the [Redis® CLI](https://redis.io/docs/ui/cli/). - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Redis™ Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) +- A [Redis® Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) -To connect to a Redis™ Database Instance in a Private Network, you can use Public Gateways in [SSH bastion](https://www.scaleway.com/en/docs/network/public-gateways/how-to/use-ssh-bastion/) mode and perform port forwarding, as Managed Databases for Redis™ are currently not compatible with the [Static NAT](/network/public-gateways/concepts/#nat) feature of [Scaleway Public Gateways](/network/public-gateways/concepts/#public-gateway). +To connect to a Redis® Database Instance in a Private Network, you can use Public Gateways in [SSH bastion](https://www.scaleway.com/en/docs/network/public-gateways/how-to/use-ssh-bastion/) mode and perform port forwarding, as Managed Databases for Redis® are currently not compatible with the [Static NAT](/network/public-gateways/concepts/#nat) feature of [Scaleway Public Gateways](/network/public-gateways/concepts/#public-gateway). -1. Click **Redis™** under **Managed Databases** on the side menu. A list of your Redis™ Database Instances displays. +1. Click **Redis®** under **Managed Databases** on the side menu. A list of your Redis® Database Instances displays. 2. Click the Database Instance name or > **More info** to access the Database Instance information page. 3. Retrieve the Database Instance IP and port from the Database Instance information section. - Alternatively, you can click the **copy icon** under **Connection** to retrieve the Redis™ CLI connection command. This already includes an IP and port. + Alternatively, you can click the **copy icon** under **Connection** to retrieve the Redis® CLI connection command. This already includes an IP and port. - You can use only one of your node IP addresses at a time to connect to your Redis™ Database Instance, as the Redis™ CLI does not support cluster mode. + You can use only one of your node IP addresses at a time to connect to your Redis® Database Instance, as the Redis® CLI does not support cluster mode. -4. Run the following command to connect to your Redis™ Database Instance. +4. Run the following command to connect to your Redis® Database Instance. In this tutorial we will use 192.0.2.1 and 6379 as the example IP and port, respectively. @@ -54,7 +54,7 @@ To connect to a Redis™ Database Instance in a Private Network, you can use Pub 5. Enter the password that you defined upon database creation. -You are now connected to your Managed Database for Redis™. +You are now connected to your Managed Database for Redis®.
* Redis is a trademark of Redis Labs Ltd. Any rights therein are reserved to Redis Labs Ltd. Any use by Scaleway is for referential purposes only and does not indicate any sponsorship, endorsement or affiliation between Redis and Scaleway. \ No newline at end of file diff --git a/managed-databases/redis/how-to/create-a-database-for-redis.mdx b/managed-databases/redis/how-to/create-a-database-for-redis.mdx index 26c73ff104..eceee34b4a 100644 --- a/managed-databases/redis/how-to/create-a-database-for-redis.mdx +++ b/managed-databases/redis/how-to/create-a-database-for-redis.mdx @@ -1,10 +1,10 @@ --- meta: - title: How to create a Redis™ Database Instance - description: Step-by-step guide to creating a Redis™ database on Scaleway. + title: How to create a Redis® Database Instance + description: Step-by-step guide to creating a Redis® database on Scaleway. content: - h1: How to create a Redis™ Database Instance - paragraph: Step-by-step guide to creating a Redis™ database on Scaleway. + h1: How to create a Redis® Database Instance + paragraph: Step-by-step guide to creating a Redis® database on Scaleway. tags: managed-database redis redis-database dates: validation: 2024-07-04 @@ -14,23 +14,23 @@ categories: - redis --- -Managed Database for Redis™* is a low-latency caching solution based on in-memory data storage. It allows you to easily set up a secure cache and lighten the load on your main database. +Managed Database for Redis®* is a low-latency caching solution based on in-memory data storage. It allows you to easily set up a secure cache and lighten the load on your main database. - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -1. Click **Redis™** under **Managed Databases** on the side menu. If you do not have a database already created, the creation page displays. -2. Click **Create Redis™ Database Instance**. The creation wizard displays. +1. Click **Redis®** under **Managed Databases** on the side menu. If you do not have a database already created, the creation page displays. +2. Click **Create Redis® Database Instance**. The creation wizard displays. 3. Complete the following steps in the wizard: - Choose an Availability Zone. This is the geographical location where your database will be deployed. - Managed Database for Redis™ are available in PAR1, PAR2, AMS1, AMS2, WAW1 and WAW2. + Managed Database for Redis® are available in PAR1, PAR2, AMS1, AMS2, WAW1 and WAW2. - - Select the version of Redis™ you wish to use on your Instance. + - Select the version of Redis® you wish to use on your Instance. - Select a database configuration. You can choose between: - **Cluster mode**: creates the database as a Cluster composed of three or more nodes. The cluster uses partitioning to split the keyspace. Each partition is replicated and can be reassigned or elected as the primary when necessary. - **Standalone**: creates a standalone database provisioned on a single node. @@ -42,9 +42,9 @@ Managed Database for Redis™* is a low-latency caching solution base - create and attach a new one - - If you want to use Private Networks, you must select the option upon creation. It is not possible to add the Redis™ Database Instance to a Private Network once it has been created. + - If you want to use Private Networks, you must select the option upon creation. It is not possible to add the Redis® Database Instance to a Private Network once it has been created. - Your private IP addresses are automatically allocated. They are managed via an IP Address Manager (IPAM). You can retrieve them on the Private Network tab of your Database Instance. To allocate IPs manually, you can use the Scaleway API and CLI, or Terraform. - - Managed Databases for Redis™ are currently not compatible with the [Static NAT](/network/public-gateways/concepts/#nat) feature of [Scaleway Public Gateways](/network/public-gateways/concepts/#public-gateway). You can use Public Gateways in [SSH bastion](https://www.scaleway.com/en/docs/network/public-gateways/how-to/use-ssh-bastion/) mode and perform port forwarding. + - Managed Databases for Redis® are currently not compatible with the [Static NAT](/network/public-gateways/concepts/#nat) feature of [Scaleway Public Gateways](/network/public-gateways/concepts/#public-gateway). You can use Public Gateways in [SSH bastion](https://www.scaleway.com/en/docs/network/public-gateways/how-to/use-ssh-bastion/) mode and perform port forwarding. - **Public network**: resources in a public network are publicly visible by default. The default Access Control List (ACL) settings allow anybody to connect to resources in your network. You can restrict access by configuring ACLs. @@ -59,7 +59,7 @@ Managed Database for Redis™* is a low-latency caching solution base - not be `scalewayadmin` or `metrics` - Enter a name and optional tags for the database. -6. Click **Create Redis™ Database Instance** to confirm your choices and launch creation. +6. Click **Create Redis® Database Instance** to confirm your choices and launch creation.
* Redis is a trademark of Redis Labs Ltd. Any rights therein are reserved to Redis Labs Ltd. Any use by Scaleway is for referential purposes only and does not indicate any sponsorship, endorsement or affiliation between Redis and Scaleway. \ No newline at end of file diff --git a/managed-databases/redis/how-to/delete-a-database-for-redis.mdx b/managed-databases/redis/how-to/delete-a-database-for-redis.mdx index 854f6c9337..44c961b9e4 100644 --- a/managed-databases/redis/how-to/delete-a-database-for-redis.mdx +++ b/managed-databases/redis/how-to/delete-a-database-for-redis.mdx @@ -1,10 +1,10 @@ --- meta: - title: How to delete a Redis™ Database Instance - description: Instructions for deleting a Redis™ database on Scaleway. + title: How to delete a Redis® Database Instance + description: Instructions for deleting a Redis® database on Scaleway. content: - h1: How to delete a Redis™ Database Instance - paragraph: Instructions for deleting a Redis™ database on Scaleway. + h1: How to delete a Redis® Database Instance + paragraph: Instructions for deleting a Redis® database on Scaleway. tags: managed-database database redis dates: validation: 2024-08-05 @@ -18,9 +18,9 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Redis™ Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) +- A [Redis® Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) -1. Click **Redis™** under **Managed Databases** on the side menu. A list of your Database Instances displays. +1. Click **Redis®** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the database name or > **More info** to access the database information page. 3. Scroll down the page to the **Delete Database Instance** section and click **Delete Database Instance**. A pop-up appears to inform that: diff --git a/managed-databases/redis/how-to/index.mdx b/managed-databases/redis/how-to/index.mdx index 65f9dce368..b0baf02fef 100644 --- a/managed-databases/redis/how-to/index.mdx +++ b/managed-databases/redis/how-to/index.mdx @@ -1,8 +1,8 @@ --- meta: - title: Managed Database for Redis™ - How Tos - description: Practical how-to guides for using Scaleway Managed Databases for Redis™. + title: Managed Database for Redis® - How Tos + description: Practical how-to guides for using Scaleway Managed Databases for Redis®. content: - h1: Managed Database for Redis™ - How Tos - paragraph: Practical how-to guides for using Scaleway Managed Databases for Redis™. + h1: Managed Database for Redis® - How Tos + paragraph: Practical how-to guides for using Scaleway Managed Databases for Redis®. --- diff --git a/managed-databases/redis/how-to/manage-allowed-ip-addresses-redis.mdx b/managed-databases/redis/how-to/manage-allowed-ip-addresses-redis.mdx index fd986fe2cd..b6dd6b7e14 100644 --- a/managed-databases/redis/how-to/manage-allowed-ip-addresses-redis.mdx +++ b/managed-databases/redis/how-to/manage-allowed-ip-addresses-redis.mdx @@ -1,10 +1,10 @@ --- meta: - title: How to manage allowed IP addresses for Managed Database for Redis™ - description: Learn how to manage allowed IP addresses for your Redis™ database. + title: How to manage allowed IP addresses for Managed Database for Redis® + description: Learn how to manage allowed IP addresses for your Redis® database. content: - h1: How to manage allowed IP addresses for Managed Database for Redis™ - paragraph: Learn how to manage allowed IP addresses for your Redis™ database. + h1: How to manage allowed IP addresses for Managed Database for Redis® + paragraph: Learn how to manage allowed IP addresses for your Redis® database. tags: managed-database ip-address redis dates: validation: 2024-07-04 @@ -14,13 +14,13 @@ categories: - redis --- -Allowed IPs restrict the IPs allowed to access your Redis™* Database Instance. The entry `0.0.0.0/0` enables any host to establish a connection. +Allowed IPs restrict the IPs allowed to access your Redis®* Database Instance. The entry `0.0.0.0/0` enables any host to establish a connection. - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Redis™ Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) +- A [Redis® Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) Allowed IP configuration is only available for public networks. @@ -28,7 +28,7 @@ Allowed IPs restrict the IPs allowed to access your Redis™* Databas ## How to add an IP address -1. Click **Redis™** under **Managed Databases** on the side menu. A list of your Database Instances displays. +1. Click **Redis®** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the database name or > **More info** to access the Database Instance information page. 3. Click **Allowed IPs** tab. 4. Click **Add IP**. The IP can be a single IP or an IP block. diff --git a/managed-databases/redis/how-to/scale-up-a-database-for-redis.mdx b/managed-databases/redis/how-to/scale-up-a-database-for-redis.mdx index c02c5f60d0..9c351a99ce 100644 --- a/managed-databases/redis/how-to/scale-up-a-database-for-redis.mdx +++ b/managed-databases/redis/how-to/scale-up-a-database-for-redis.mdx @@ -1,10 +1,10 @@ --- meta: - title: How to scale up a Redis™ Database Instance - description: Steps to scale up your Redis™ Database Instance on Scaleway. + title: How to scale up a Redis® Database Instance + description: Steps to scale up your Redis® Database Instance on Scaleway. content: - h1: How to scale up a Redis™ Database Instance - paragraph: Steps to scale up your Redis™ Database Instance on Scaleway. + h1: How to scale up a Redis® Database Instance + paragraph: Steps to scale up your Redis® Database Instance on Scaleway. tags: managed-database redis database dates: validation: 2024-07-04 @@ -14,7 +14,7 @@ categories: - postgresql-and-mysql --- -If you want to scale up the size of your Redis™* Database Instance, you can edit your node settings to either: +If you want to scale up the size of your Redis®* Database Instance, you can edit your node settings to either: - **Scale vertically**: upgrade to a bigger node type to allow increased traffic for the same endpoint. - **Scale horizontally**: add more nodes to your Database Instance to increase your number of endpoints and distribute cache. This setting is only available for Database Instances in cluster mode. @@ -25,9 +25,9 @@ If you want to scale up the size of your Redis™* Database Instance, - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Redis™ Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) +- A [Redis® Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) -1. Click **Redis™** under **Managed Databases** on the side menu. A list of your Database Instances displays. +1. Click **Redis®** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the database name or > **More info** to access the Database Instances information page. 3. Scroll down the page to the **Node Settings** section. 4. Click **Scale vertically**. A pop-up appears. @@ -42,9 +42,9 @@ If you want to scale up the size of your Redis™* Database Instance, - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Redis™ Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) in [cluster mode](/managed-databases/redis/concepts/#cluster-mode) +- A [Redis® Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) in [cluster mode](/managed-databases/redis/concepts/#cluster-mode) -1. Click **Redis™** under **Database** on the side menu. A list of your Database Instances displays. +1. Click **Redis®** under **Database** on the side menu. A list of your Database Instances displays. 2. Click the database name or > **More info** to access the Database Instance information page. 3. Scroll down the page to the **Node Settings** section. 4. Click **Scale horizontally**. A pop-up appears. diff --git a/managed-databases/redis/index.mdx b/managed-databases/redis/index.mdx index 690b32070a..30d26bfb10 100644 --- a/managed-databases/redis/index.mdx +++ b/managed-databases/redis/index.mdx @@ -1,15 +1,15 @@ --- meta: - title: Managed Database for Redis™ Documentation - description: Dive into Scaleway Managed Database for Redis™ with our quickstart guides, how-tos, tutorials and more. + title: Managed Database for Redis® Documentation + description: Dive into Scaleway Managed Database for Redis® with our quickstart guides, how-tos, tutorials and more. --- ## Getting Started @@ -18,28 +18,28 @@ meta: @@ -50,7 +50,7 @@ meta: @@ -58,15 +58,15 @@ meta: ## Changelog diff --git a/managed-databases/redis/quickstart.mdx b/managed-databases/redis/quickstart.mdx index 10339ac95f..864fadeb02 100644 --- a/managed-databases/redis/quickstart.mdx +++ b/managed-databases/redis/quickstart.mdx @@ -1,10 +1,10 @@ --- meta: - title: Managed Database for Redis™ - Quickstart - description: Get started quickly with Scaleway Managed Databases for Redis™. + title: Managed Database for Redis® - Quickstart + description: Get started quickly with Scaleway Managed Databases for Redis®. content: - h1: Managed Database for Redis™ - Quickstart - paragraph: Get started quickly with Scaleway Managed Databases for Redis™. + h1: Managed Database for Redis® - Quickstart + paragraph: Get started quickly with Scaleway Managed Databases for Redis®. tags: managed-database redis dates: validation: 2024-07-04 @@ -14,25 +14,25 @@ categories: - postgresql-and-mysql --- -## How to create a Redis™ Database Instance +## How to create a Redis® Database Instance -Managed Database for Redis™ is a low-latency caching solution based on in-memory data storage. It allows you to easily set up a secure cache and lighten the load on your main database. +Managed Database for Redis® is a low-latency caching solution based on in-memory data storage. It allows you to easily set up a secure cache and lighten the load on your main database. - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -1. Click **Redis™** under **Managed Databases** on the side menu. If you do not have a database already created, the creation page displays. -2. Click **Create Redis™ Database Instance**. The creation wizard displays. +1. Click **Redis®** under **Managed Databases** on the side menu. If you do not have a database already created, the creation page displays. +2. Click **Create Redis® Database Instance**. The creation wizard displays. 3. Complete the following steps in the wizard: - Choose an Availability Zone. This is the geographical location where your database will be deployed. - Managed Database for Redis™ are available in PAR1, PAR2, AMS1, AMS2, WAW1 and WAW2. + Managed Database for Redis® are available in PAR1, PAR2, AMS1, AMS2, WAW1 and WAW2. - - Select the version of Redis™ you wish to use on your Instance. + - Select the version of Redis® you wish to use on your Instance. - Select a database configuration. You can choose between: - **Cluster mode**: creates the database as a cluster composed of three or more nodes. The cluster uses partitioning to split the keyspace. Each partition is replicated and can be reassigned or elected as the primary when necessary. - **Standalone**: creates a standalone database provisioned on a single node. @@ -44,7 +44,7 @@ Managed Database for Redis™ is a low-latency caching solution based on in-memo - create and attach a new one - If you want to use Private Networks, you must select the option upon creation. It is not possible to add the Redis™ Database Instance to a Private Network once it has been created. + If you want to use Private Networks, you must select the option upon creation. It is not possible to add the Redis® Database Instance to a Private Network once it has been created. @@ -63,17 +63,17 @@ Managed Database for Redis™ is a low-latency caching solution based on in-memo - not be `scalewayadmin` or `metrics` - Enter a name and optional tags for the database. -6. Click **Create Redis™ Database Instance** to confirm your choices and launch creation. +6. Click **Create Redis® Database Instance** to confirm your choices and launch creation. -## How to delete a Redis™ Database Instance +## How to delete a Redis® Database Instance - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Redis™ Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) +- A [Redis® Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) -1. Click **Redis™** under **Managed Databases** on the side menu. A list of your Database Instances displays. +1. Click **Redis®** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the database name or > **More info** to access the database information page. 3. Scroll down the page to the **Delete Database Instance** section and click **Delete Database Instance**. A pop-up appears to inform that: diff --git a/managed-databases/redis/reference-content/default-user-permissions.mdx b/managed-databases/redis/reference-content/default-user-permissions.mdx index 026b15ef09..51ab885e65 100644 --- a/managed-databases/redis/reference-content/default-user-permissions.mdx +++ b/managed-databases/redis/reference-content/default-user-permissions.mdx @@ -1,10 +1,10 @@ --- meta: title: Understanding default user permissions - description: Reference guide to default user permissions for Redis™ databases. + description: Reference guide to default user permissions for Redis® databases. content: h1: Understanding default user permissions - paragraph: Reference guide to default user permissions for Redis™ databases. + paragraph: Reference guide to default user permissions for Redis® databases. tags: databases user redis username password dates: validation: 2024-04-15 @@ -13,7 +13,7 @@ categories: - redis --- -When you create a Redis™* Database Instance, you have to specify a user. It will be created with the following permissions: +When you create a Redis®* Database Instance, you have to specify a user. It will be created with the following permissions: ``` +client +cluster diff --git a/managed-databases/redis/reference-content/ensuring-data-persistence.mdx b/managed-databases/redis/reference-content/ensuring-data-persistence.mdx index 35e6d69f60..ce7195e19e 100644 --- a/managed-databases/redis/reference-content/ensuring-data-persistence.mdx +++ b/managed-databases/redis/reference-content/ensuring-data-persistence.mdx @@ -1,10 +1,10 @@ --- meta: title: Ensuring data persistence - description: Learn how to ensure data persistence in your Scaleway Redis™ database. + description: Learn how to ensure data persistence in your Scaleway Redis® database. content: h1: Ensuring data persistence - paragraph: Learn how to ensure data persistence in your Scaleway Redis™ database. + paragraph: Learn how to ensure data persistence in your Scaleway Redis® database. tags: databases user redis username password dates: validation: 2024-04-15 @@ -17,21 +17,21 @@ Data persistence ensures that the data from your applications is saved, in memor When data is stored in memory, and no data persistence strategy is put in place, the data will be gone any time the compute process is stopped. -To avoid this, Redis™* natively supports persistence by performing [snapshots](https://redis.io/docs/management/persistence/). +To avoid this, Redis®* natively supports persistence by performing [snapshots](https://redis.io/docs/management/persistence/). -This feature is supported and managed by Scaleway with Managed Databases for Redis™. +This feature is supported and managed by Scaleway with Managed Databases for Redis®. Furthermore, you can leverage the [cluster mode](/faq/databases-for-redis/#what-is-the-logic-behind-the-cluster-mode) to ensure the durability of your data. - Scaleway Managed Database for Redis™ is currently best suited for caching use cases. The data persistence mechanism presented on this page do not guarantee data recovery in case of incident. + Scaleway Managed Database for Redis® is currently best suited for caching use cases. The data persistence mechanism presented on this page do not guarantee data recovery in case of incident. ## Snapshots Snapshots are available by default with a fixed configuration. -When you create a new Redis™ Database Instance, a Redis™ snapshot is also automatically created within specified intervals. These are: +When you create a new Redis® Database Instance, a Redis® snapshot is also automatically created within specified intervals. These are: - 900 seconds if one key has been updated - 300 seconds if 10 keys have been updated @@ -43,7 +43,7 @@ When you create a new Redis™ Database Instance, a Redis™ snapshot is also au ## Cluster mode -If you want to benefit from fault-tolerant architecture in some use cases, we recommend you deploy Redis™ in [cluster mode](/faq/databases-for-redis/#what-is-the-logic-behind-the-cluster-mode), where each primary node is deployed with a replica node. +If you want to benefit from fault-tolerant architecture in some use cases, we recommend you deploy Redis® in [cluster mode](/faq/databases-for-redis/#what-is-the-logic-behind-the-cluster-mode), where each primary node is deployed with a replica node. A Redis cluster contains a minimum of three nodes and up to six nodes. Each node contains a source and a replica. The cluster nodes use hash partitioning to split the keyspace into key slots. Each replica copies the data of a specific source and can be reassigned to replicate another source or be elected as a source node if needed. This is recommended for scaling as the operation is spread across multiple nodes instead of having a single entry point. @@ -53,7 +53,7 @@ The Scaleway Managed Databases team is currently working on a High Availability This feature is expected in October 2023. -Follow our [changelog](/changelog/) to remain up-to-date with the latest improvements in Managed Databases for Redis™. +Follow our [changelog](/changelog/) to remain up-to-date with the latest improvements in Managed Databases for Redis®.
* Redis is a trademark of Redis Labs Ltd. Any rights therein are reserved to Redis Labs Ltd. Any use by Scaleway is for referential purposes only and does not indicate any sponsorship, endorsement or affiliation between Redis and Scaleway. \ No newline at end of file diff --git a/managed-databases/redis/reference-content/index.mdx b/managed-databases/redis/reference-content/index.mdx index f0383cbd58..90ce505701 100644 --- a/managed-databases/redis/reference-content/index.mdx +++ b/managed-databases/redis/reference-content/index.mdx @@ -1,8 +1,8 @@ --- meta: - title: Managed Database for Redis™ - Additional content - description: Detailed additional content for Scaleway Managed Databases for Redis™. + title: Managed Database for Redis® - Additional content + description: Detailed additional content for Scaleway Managed Databases for Redis®. content: - h1: Managed Database for Redis™ - Additional content - paragraph: Detailed additional content for Scaleway Managed Databases for Redis™. + h1: Managed Database for Redis® - Additional content + paragraph: Detailed additional content for Scaleway Managed Databases for Redis®. --- \ No newline at end of file diff --git a/menu/changelogs.json b/menu/changelogs.json index 0dd866f294..b9d8d120cb 100644 --- a/menu/changelogs.json +++ b/menu/changelogs.json @@ -163,8 +163,8 @@ "label": "PostgreSQL and MySQL" }, { - "category": "redistm", - "label": "Redis™" + "category": "redis", + "label": "Redis®" } ], "category": "databases", diff --git a/menu/navigation.json b/menu/navigation.json index b09ae73cd4..b043cf28ec 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -2270,11 +2270,11 @@ { "items": [ { - "label": "Create a Redis™ Database Instance", + "label": "Create a Redis® Database Instance", "slug": "create-a-database-for-redis" }, { - "label": "Connect to a Redis™ Database Instance", + "label": "Connect to a Redis® Database Instance", "slug": "connect-to-redis-database-instance" }, { @@ -2282,7 +2282,7 @@ "slug": "manage-allowed-ip-addresses-redis" }, { - "label": "Scale up a Redis™ Database Instance", + "label": "Scale up a Redis® Database Instance", "slug": "scale-up-a-database-for-redis" }, { @@ -2290,7 +2290,7 @@ "slug": "configure-advanced-settings-redis" }, { - "label": "Delete a Redis™ Database Instance", + "label": "Delete a Redis® Database Instance", "slug": "delete-a-database-for-redis" } ], @@ -2300,7 +2300,7 @@ { "items": [ { - "label": "Managed Database for Redis™ API Reference", + "label": "Managed Database for Redis® API Reference", "slug": "https://www.scaleway.com/en/developers/api/managed-database-redis/" }, { @@ -2330,7 +2330,7 @@ "slug": "reference-content" } ], - "label": "Redis™", + "label": "Redis®", "slug": "redis" } ], @@ -2922,15 +2922,15 @@ "slug": "api-cli" }, { - "items": [ - { - "label": "Public connectivity: best practices", - "slug": "public-connectivity-best-practices" - } - ], - "label": "Additional Content", - "slug": "reference-content" - } + "items": [ + { + "label": "Public connectivity: best practices", + "slug": "public-connectivity-best-practices" + } + ], + "label": "Additional Content", + "slug": "reference-content" + } ], "label": "IPAM", "slug": "ipam" diff --git a/network/vpc/how-to/attach-resources-to-pn.mdx b/network/vpc/how-to/attach-resources-to-pn.mdx index b52e6281c8..1c53c8e858 100644 --- a/network/vpc/how-to/attach-resources-to-pn.mdx +++ b/network/vpc/how-to/attach-resources-to-pn.mdx @@ -27,7 +27,7 @@ The following resource types can be attached to a Private Network: - Managed Databases for PostgreSQL and MySQL - Kubernetes Kapsules and Managed Databases for Redis™ are also compatible with Private Networks, but they can only be attached to a Private Network at the time of creating the resource. It is not possible to attach a cluster or Redis™ database to a Private Network after its creation, or change the attached Private Network. + Kubernetes Kapsules and Managed Databases for Redis® are also compatible with Private Networks, but they can only be attached to a Private Network at the time of creating the resource. It is not possible to attach a cluster or Redis® database to a Private Network after its creation, or change the attached Private Network. @@ -84,7 +84,7 @@ You can also attach a resource to a Private Network from the resource's own sect - [Load Balancer](/network/load-balancer/how-to/use-with-private-network/) - [Public Gateway](/network/vpc/how-to/create-private-network/#how-to-attach-and-detach-resources-tofrom-a-private-network) -Note that for Kubernetes Kapsules and Managed Databases for Redis™, you can only attach the resource to a Private Network at the time of creating the resource itself. +Note that for Kubernetes Kapsules and Managed Databases for Redis®, you can only attach the resource to a Private Network at the time of creating the resource itself. ## How to view the resource's IP address diff --git a/network/vpc/reference-content/getting-most-private-networks.mdx b/network/vpc/reference-content/getting-most-private-networks.mdx index 2872bf7e65..a433dd43bf 100644 --- a/network/vpc/reference-content/getting-most-private-networks.mdx +++ b/network/vpc/reference-content/getting-most-private-networks.mdx @@ -112,13 +112,13 @@ Different types of Scaleway resources may have different requirements and possib | Documentation | [Go](/compute/instances/how-to/use-private-networks/) | [Go](/bare-metal/elastic-metal/how-to/use-private-networks/) | [Go](/containers/kubernetes/reference-content/secure-cluster-with-private-network/#why-have-a-private-network-for-your-kubernetes-kapsule-cluster) | [Go](/ai-data/managed-inference/how-to/managed-inference-with-private-network/) | -| | Managed Database | Managed Database for Redis™ | Public Gateways | Load Balancer | +| | Managed Database | Managed Database for Redis® | Public Gateways | Load Balancer | |------------------------------|------------------|-----------------------------|-----------------|---------------| | Max attached PNs | 1 | 1 | 8 | 8 | | Mandatory PN | No | No | No | No | | Compatible with private IPv6 | No | No | No | No | | Compatible with reserved IPs | No | No | Yes | Yes | | Additional information | Must have at least one of
private and/or public endpoint | Must have at least one of
private and/or public endpoint | -- | Private LBs must have a PN | -| Documentation | [Go](/managed-databases/postgresql-and-mysql/how-to/connect-database-private-network/) | [Go](/faq/databases-for-redis/#what-is-the-private-networks-feature-for-redistm-database-instances) | [Go](/network/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network) | [Go](/network/load-balancer/how-to/use-with-private-network/) +| Documentation | [Go](/managed-databases/postgresql-and-mysql/how-to/connect-database-private-network/) | [Go](/faq/databases-for-redis/#what-is-the-private-networks-feature-for-redis-database-instances) | [Go](/network/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network) | [Go](/network/load-balancer/how-to/use-with-private-network/) diff --git a/network/vpc/troubleshooting/vpc-limitations.mdx b/network/vpc/troubleshooting/vpc-limitations.mdx index a8f4b3c74f..afb377799e 100644 --- a/network/vpc/troubleshooting/vpc-limitations.mdx +++ b/network/vpc/troubleshooting/vpc-limitations.mdx @@ -24,7 +24,7 @@ This page sets out some current limitations of Scaleway's VPC. - Load Balancers - Public Gateways - Managed Databases for PostgreSQL and MySQL - - Managed Databases for Redis™ (only during the process of creating the database) + - Managed Databases for Redis® (only during the process of creating the database) - Kubernetes Kapsule (only during the process of creating the Kapsule cluster) - Private Networks are not supported on some legacy Instance offers which have reached EOL, e.g. `VC1`, `START1` and `X64-*GB`. Note that all Instance offers in the [current product catalogue](https://www.scaleway.com/en/pricing/?tags=compute) are supported. - Managed Databases are not currently compatible with VPC routing. The VPC cannot automatically route between Managed Databases on different Private Networks, or (for example) between a Managed Database on one Private Network and an Instance on a different Private Network. diff --git a/tutorials/erpnext/index.mdx b/tutorials/erpnext/index.mdx index f95f4d15ca..a68056ab38 100644 --- a/tutorials/erpnext/index.mdx +++ b/tutorials/erpnext/index.mdx @@ -180,15 +180,15 @@ All the following steps will be executed from the newly created user account and cd /home/timmy ``` -### Installing Redis™ +### Installing Redis® -ERPNext uses the caching features of [Redis™](https://redis.io/) to increase database performance. +ERPNext uses the caching features of [Redis®](https://redis.io/) to increase database performance. 1. Install it using the `apt` package manager: ``` sudo apt install redis-server ``` -2. Configure Redis™ to start automatically during system boot: +2. Configure Redis® to start automatically during system boot: ``` sudo systemctl enable redis-server.service ``` diff --git a/tutorials/use-managed-redis-with-mysql/index.mdx b/tutorials/use-managed-redis-with-mysql/index.mdx index 941ebecf81..4c1f8fd8c1 100644 --- a/tutorials/use-managed-redis-with-mysql/index.mdx +++ b/tutorials/use-managed-redis-with-mysql/index.mdx @@ -1,10 +1,10 @@ --- meta: - title: Use Scaleway Managed Redis™ for MySQL caching with Entity Framework - description: In this tutorial, you will learn to use Scaleway Redis™ as a record cache for Scaleway MySQL + title: Use Scaleway Managed Redis® for MySQL caching with Entity Framework + description: In this tutorial, you will learn to use Scaleway Redis® as a record cache for Scaleway MySQL content: - h1: Use Scaleway Managed Redis™ for MySQL caching with Entity Framework - paragraph: In this tutorial, you will learn to use Scaleway Redis™ as a record cache for Scaleway MySQL. + h1: Use Scaleway Managed Redis® for MySQL caching with Entity Framework + paragraph: In this tutorial, you will learn to use Scaleway Redis® as a record cache for Scaleway MySQL. tags: mysql redis entity-framework cache categories: - postgresql-and-mysql @@ -13,7 +13,7 @@ validation: 2024-05-27 posted: 2023-11-25 --- -This tutorial demonstrates the integration of a [Scaleway Redis™](https://www.scaleway.com/en/managed-database-for-redistm/) Instance as a record cache (commonly referred to as a second-level cache) for an application using a [Scaleway MySQL](https://www.scaleway.com/fr/database/) Instance through [Entity Framework](https://learn.microsoft.com/en-us/ef/). +This tutorial demonstrates the integration of a [Scaleway Redis®](https://www.scaleway.com/en/managed-database-for-redis/) Instance as a record cache (commonly referred to as a second-level cache) for an application using a [Scaleway MySQL](https://www.scaleway.com/fr/database/) Instance through [Entity Framework](https://learn.microsoft.com/en-us/ef/). While the principles discussed apply to various technologies and data stores, the examples and demonstrations on this page specifically use MySQL as the database, Redis as the cache, and Entity Framework for .NET as the Object-Relational Mapping (ORM) tool. @@ -23,7 +23,7 @@ This tutorial demonstrates the integration of a [Scaleway Redis™](https://www. - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Redis™ Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) +- A [Redis® Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) - A [MySQL Database Instance](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) - Installed the [.NET 7 SDK](https://dotnet.microsoft.com/en-us/download/dotnet/7.0) @@ -42,7 +42,7 @@ To initiate a new .NET project, follow these steps using the dotnet CLI: 2. Navigate to your newly created project folder and install dependencies for the data stores: - `Pomelo.EntityFrameworkCore.MySql` is the database driver for MySQL in Entity Framework. - `EFCoreSecondLevelCacheInterceptor` is the second-level cache extension for Entity Framework. - - `EasyCaching.Redis` is a Redis™ driver for .NET. + - `EasyCaching.Redis` is a Redis® driver for .NET. - `EasyCaching.Serialization.MessagePack`: provides serialization support for EasyCaching. ``` @@ -114,11 +114,11 @@ Follow these steps to configure your MySQL database with Entity Framework: Replace the connection string placeholder with the one from the previous step in that snippet. -## Configure the Redis™ cache +## Configure the Redis® cache -Follow these steps to configure your Redis™ cache with Entity Framework: +Follow these steps to configure your Redis® cache with Entity Framework: -1. Get the public IP, port, and username for your Redis™ Instance. Locate this information on the **Database Instance Information** page of your Instance in the [Scaleway console](https://console.scaleway.com/redis/clusters), under **Public endpoints**. +1. Get the public IP, port, and username for your Redis® Instance. Locate this information on the **Database Instance Information** page of your Instance in the [Scaleway console](https://console.scaleway.com/redis/clusters), under **Public endpoints**. 2. Download the TLS certificate using the button and store it in your project folder. @@ -128,7 +128,7 @@ Follow these steps to configure your Redis™ cache with Entity Framework: :,user=,password=,ssl=True ``` -4. During application startup, configure the EasyCaching library to connect to your Redis™ Database Instance, and configure it as the second-level cache for Entity Framework. Insert this snippet at the end of `Program.cs`: +4. During application startup, configure the EasyCaching library to connect to your Redis® Database Instance, and configure it as the second-level cache for Entity Framework. Insert this snippet at the end of `Program.cs`: ```csharp builder.Services.AddEasyCaching(options => { @@ -153,7 +153,7 @@ Follow these steps to configure your Redis™ cache with Entity Framework: ## Create the app -Your application is now fully configured to use the Redis™ Database Instance as a second-level cache for the Scaleway MySQL Instance. To test the setup, create a couple of API endpoints. +Your application is now fully configured to use the Redis® Database Instance as a second-level cache for the Scaleway MySQL Instance. To test the setup, create a couple of API endpoints. 1. Define endpoints to interact with your Product database model for listing, retrieving, and adding `ProductModel`s. Add the following snippet at the end of Program.cs: ```csharp @@ -174,7 +174,7 @@ Your application is now fully configured to use the Redis™ Database Instance a ``` - Use `.Cacheable()` on Entity Framework queries to leverage the Redis™ second-level cache: + Use `.Cacheable()` on Entity Framework queries to leverage the Redis® second-level cache: - During a query, Entity Framework checks the cache for recent executions and retrieves results if available. Otherwise, it executes the query using the database and stores the result in the cache. - Any DML operation invalidates the cache on the related rows. To further configure the second-level cache behavior, refer to the [package extension documentation](https://github.com/VahidN/EFCoreSecondLevelCacheInterceptor).