Revert "fix(rdb): summer cleaning"

changelog/databases/november2022/2022-11-18-mysqlpgsql-changed-read-replica.mdx

@@ -9,4 +9,4 @@ category: databases
 product: postgresql-and-mysql
 ---
 
-Add up to three Read Replicas to your PostgreSQL or MySQL Instance and offload your main node from read requests. Follow the how-to to [create your first Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/).
+Add up to three Read Replicas to your PostgreSQL or MySQL Instance and offload your main node from read requests. Follow the how-to to [create your first Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/).

changelog/databases/september2022/2022-09-13-pnm-added-read-replica.mdx

@@ -9,4 +9,4 @@ category: databases
 product: postgresql-and-mysql
 ---
 
-Read Replicas are now available for Managed Database for PostgreSQL and MySQL. Follow the how-to to [create your first Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/).
+Read Replicas are now available for Managed Database for PostgreSQL and MySQL. Follow the how-to to [create your first Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/).

changelog/february2025/2025-02-24-mongodb-added-vpc-x-managed-mongodbr-integration.mdx

@@ -9,5 +9,5 @@ category: databases
 product: mongodb
 ---
 
-VPC is now integrated with Managed MongoDB®, allowing you to attach a database instance to a Private Network. Refer to [the dedicated documentation](/managed-mongodb-databases/how-to/connect-database-instance/#how-to-connect-to-a-database-instance-through-a-private-network/) to learn how to set it up.
+VPC is now integrated with Managed MongoDB®, allowing you to attach a database instance to a Private Network. Refer to [the dedicated documentation](/managed-mongodb-databases/how-to/connect-database-private-network/) to learn how to set it up.
 

changelog/september2023/2023-09-19-postgresql-and-mysql-added-cross-availability-zone-read.mdx

@@ -10,6 +10,6 @@ product: postgresql-and-mysql
 ---
 
  The Cross-AZ Read Replica feature ensures your data is replicated in a dedicated read-only node, which is located in another AZ within the same Region as your main node.
-
- For more information, refer to the [How to create Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/) documentation page.
+  
+ For more information, refer to the [How to create Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/) documentation page.
 

menu/navigation.json

@@ -2122,41 +2122,57 @@
                     "label": "Connect to a Database Instance",
                     "slug": "connect-database-instance"
                   },
+                  {
+                    "label": "Connect a Database Instance to a Private Network",
+                    "slug": "connect-database-private-network"
+                  },
                   {
                     "label": "Create a database",
                     "slug": "add-a-database"
                   },
                   {
-                    "label": "Manage users",
-                    "slug": "manage-users"
+                    "label": "Add users",
+                    "slug": "add-users"
                   },
                   {
-                    "label": "Manage volumes",
-                    "slug": "manage-volumes"
+                    "label": "Manage permissions",
+                    "slug": "manage-permissions"
                   },
                   {
-                    "label": "Manage nodes",
-                    "slug": "manage-nodes"
+                    "label": "Manage allowed IPs",
+                    "slug": "manage-allowed-ip-addresses"
                   },
                   {
-                    "label": "Manage backups",
-                    "slug": "manage-backups"
+                    "label": "Monitor Database Instances with Cockpit",
+                    "slug": "monitor-databases-cockpit"
                   },
                   {
-                    "label": "Manage snapshots",
-                    "slug": "manage-snapshots"
+                    "label": "Change the volume type",
+                    "slug": "change-volume-type"
                   },
                   {
-                    "label": "Manage Read Replicas",
-                    "slug": "manage-read-replicas"
+                    "label": "Enable Autobackup",
+                    "slug": "enable-autobackup"
+                  },
+                  {
+                    "label": "Manage manual backups",
+                    "slug": "manage-manual-backups"
+                  },
+                  {
+                    "label": "Manage snapshots",
+                    "slug": "manage-snapshots"
                   },
                   {
                     "label": "Clone a Database Instance",
                     "slug": "clone-a-database-instance"
                   },
                   {
-                    "label": "Manage allowed IPs",
-                    "slug": "manage-allowed-ip-addresses"
+                    "label": "Create Read Replicas",
+                    "slug": "create-read-replica"
+                  },
+                  {
+                    "label": "Manage Read Replicas",
+                    "slug": "manage-read-replica"
                   },
                   {
                     "label": "Configure advanced settings",
@@ -2167,13 +2183,17 @@
                     "slug": "renew-tls-certificate"
                   },
                   {
-                    "label": "Monitor Database Instances with Cockpit",
-                    "slug": "monitor-databases-cockpit"
+                    "label": "Upgrade a Database Instance",
+                    "slug": "upgrade-a-database"
                   },
                   {
-                    "label": "Upgrade Database Instance engine versions",
+                    "label": "Upgrade Database Instance engine version",
                     "slug": "upgrade-version"
                   },
+                  {
+                    "label": "Enable High Availability",
+                    "slug": "enable-high-availability"
+                  },
                   {
                     "label": "Apply scheduled maintenance",
                     "slug": "apply-maintenance"

pages/kubernetes/reference-content/secure-cluster-with-private-network.mdx

@@ -73,7 +73,7 @@ Yes, they are. Since July 2023, the automatic allocation of IP addresses via IPA
 
 For any new Private Networks you create and attach to Managed Databases after July 2023, your private IP addresses are automatically allocated.
 
-If you have set up Private Network endpoints for your Managed Databases before July 2023, and want to connect to Kapsule via a Private Network, you must first delete your old Private Network endpoint. Then, you can create a new one, either via the [Scaleway console](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance/#how-to-connect-to-a-database-instance-through-a-private-network/#how-to-attach-a-database-instance-to-a-private-network) or API.
+If you have set up Private Network endpoints for your Managed Databases before July 2023, and want to connect to Kapsule via a Private Network, you must first delete your old private network endpoint. Then, you can create a new one, either via the [Scaleway console](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network/#how-to-attach-a-database-instance-to-a-private-network) or API.
 
 In the example below, we show you how to do so via the API. We specify the automated configuration of your Private Network via IPAM using `"ipam_config": {},`.
 

pages/managed-databases-for-postgresql-and-mysql/api-cli/using-pgcron.mdx

@@ -37,7 +37,7 @@ CREATE EXTENSION
 To fully use the extension, you must grant read/write rights to the user who will be running the `pg_cron` functions to manage jobs on the database.
 
 <Message type="note">
-  Refer to the [How to add users to a PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/how-to/manage-users) documentation for more information.
+  Refer to the [How to add users to a PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/how-to/add-users) documentation for more information.
 </Message>
 
 ## Scheduling jobs

pages/managed-databases-for-postgresql-and-mysql/concepts.mdx

@@ -76,7 +76,7 @@ The HA standby node is linked to the main node, using synchronous replication. S
 </Message>
 
 <Message type="note">
-  HA standby nodes are not accessible to users unless the main node becomes unavailable and the standby takes over. If you wish to run queries on a read-only node, you can use [Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/).
+  HA standby nodes are not accessible to users unless the main node becomes unavailable and the standby takes over. If you wish to run queries on a read-only node, you can use [Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/).
 </Message>
 
 ## Local Storage

pages/managed-databases-for-postgresql-and-mysql/faq.mdx

@@ -110,15 +110,15 @@ Database Instances supports IP provisioning using IPAM. With this mode, a privat
 
 No, the second node created when you activate the HA on your Managed Database Instance is a hot standby. This node allows a fast failover in case of issues on the primary node.
 
-You can use the [Read Replica feature](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/).
+You can use the [Read Replica feature](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/).
 
 ## If my main node becomes unavailable, is my Read Replica automatically promoted to the main node?
 
 No. To promote a Read Replica to the main node, follow the [How to promote a Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replica/#how-to-promote-a-read-replica) procedure.
 
 ## Why is my number of active backups/snapshots exceeding the quota?
 
-When [autobackup](/managed-databases-for-postgresql-and-mysql/how-to/manage-backups), or autosnapshot, is enabled for your local or Block volumes, regular quota limitations for backups and snapshots do not apply.
+When [autobackup](/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup), or autosnapshot, is enabled for your local or Block volumes, regular quota limitations for backups and snapshots do not apply.
 
 Quotas exist to protect Scaleway from abuse, and to protect your Scaleway resources from the unlikely event of malicious behavior by users in your Organization.
 

pages/managed-databases-for-postgresql-and-mysql/how-to/manage-users.mdx → pages/managed-databases-for-postgresql-and-mysql/how-to/add-users.mdx

@@ -1,9 +1,9 @@
 ---
-title: How to manage database users
-description: Steps to add and manage users on your PostgreSQL and MySQL databases.
+title: How to add users to a PostgreSQL or MySQL Database Instance
+description: Steps to add users to your PostgreSQL and MySQL databases.
 tags: managed-database database postgresql mysql database-instance
 dates:
-  validation: 2025-08-07
+  validation: 2025-02-11
   posted: 2019-09-21
 ---
 import Requirements from '@macros/iam/requirements.mdx'
@@ -17,8 +17,6 @@ Users can connect to a database and access its data. Each one has a different se
 - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
 - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/)
 
-## How to create a user
-
 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays.
 2. Select the geographical region of the Instance you want to manage from the drop-down.
 3. Click the database name or <Icon name="more" /> > **More info** to access the Database Instance information page.
@@ -38,33 +36,10 @@ Users can connect to a database and access its data. Each one has a different se
       You can select the permission type in the Permissions tab.
 
     </Message>
-
-    <Message type="important">
-      PostgreSQL Permissions are applied to existing items **at the moment the configuration is set**. They cannot be applied to any items created afterward.
-      When you add database objects like tables or sequences, your configured permissions are automatically set to **Custom**. The **Custom** setting ensures that your permissions are still valid for items created before you reconfigured your Database.
-      You can use [PostgreSQL default privileges](https://www.postgresql.org/docs/current/sql-alterdefaultprivileges.html) to set default privileges for future objects.
-    </Message>
 8. Click **Create user** to confirm.
 
     Once the user is created, it is displayed in the user list.
 
 To update the password, the permissions or delete the user, click <Icon name="more" /> to display the respective options.
 
-## Set permissions for an existing user
 
-Permissions define the actions a user can perform on a logical database. A database user is automatically generated when you create your Database Instance, to whom the permissions are attributed. However, newly created users have no permissions by default.
-
-1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays.
-2. Select the geographical region of the Instance you want to manage from the drop-down.
-3. Click the database name or <Icon name="more" /> > **More info** to access the Database Instance information page.
-4. Go to the **Users** tab. A list of users displays.
-5. Click <Icon name="more" /> > **Update permissions** to open the user permissions panel.
-6. Select the appropriate permissions for each database.
-    <Message type="note">
-      Three types of permissions are available:
-        - **None:** No access to the database
-        - **Read:** Allow users to read tables and fields in a database
-        - **Read/Write:** Allow users to read/write content in databases
-        - **All:** Allows the creation of schemas and tables.
-    </Message>
-7. Click **Update user** to confirm.

pages/managed-databases-for-postgresql-and-mysql/how-to/manage-volumes.mdx → pages/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type.mdx

@@ -1,32 +1,33 @@
 ---
-title: How to manage volumes
-description: This page explains how to manage the volumes of your Database Instances
+title: How to change the volume type of your Database
+description: This page explains how to change the volume type of your Database
 tags: managed-database database volume-type
 dates:
-  validation: 2025-08-07
-  posted: 2025-08-07
+  validation: 2025-07-15
+  posted: 2021-03-10
 ---
 import Requirements from '@macros/iam/requirements.mdx'
 
 
+It is possible to change your [volume type](/managed-databases-for-postgresql-and-mysql/concepts/#volume-type) anytime in the Scaleway console.
+
 <Requirements />
 
 - A Scaleway account logged into the [console](https://console.scaleway.com)
 - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
 - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) with local Storage
 
-
-## How to change the volume type
-
-### Important information
+## Important information
 
 Since there are different types of volumes for Database Instances, make sure you are aware of the following information before changing the volume type:
 
 - When autobackup is enabled for your local or Block volumes, regular quota limitations for backups and snapshots do not apply. Refer to the [Managed Databases FAQ page](/managed-databases-for-postgresql-and-mysql/faq/#why-is-my-number-of-active-backupssnapshots-exceeding-the-quota) for more information.
-- When switching from a local volume to a Block volume, and if [Autobackup](/managed-databases-for-postgresql-and-mysql/how-to/manage-backups/) is enabled, be aware that the snapshot type will change. Local volumes use logical backups, whereas Block Storage employs snapshots. Both types are priced at €0.03 per GB per month, but their distinct backup methods affect storage space differently, influencing the final monthly cost based on your usage.
+- When switching from a local volume to a Block volume, and if [Autobackup](/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup/) is enabled, be aware that the snapshot type will change. Local volumes use logical backups, whereas Block Storage employs snapshots. Both types are priced at €0.03 per GB per month, but their distinct backup methods affect storage space differently, influencing the final monthly cost based on your usage.
 - Disk size cannot be reduced. Therefore, when switching from local to Block, the volume size remains the same by default.
 - When switching from a Block to a local volume, make sure to select a node with a local Storage with size equal or greater than your current Block Storage. If you choose a Database Instance type with a local volume larger than your current block volume, you will be billed for the full capacity of the Database Instance.
-It is possible to change your [volume type](/managed-databases-for-postgresql-and-mysql/concepts/#volume-type) anytime in the Scaleway console.
+
+
+## How to change the volume type
 
 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays.
 2. Select the geographical region of the Instance you want to manage from the drop-down.
@@ -41,9 +42,10 @@ It is possible to change your [volume type](/managed-databases-for-postgresql-an
 5. Select **Block Storage** from the drop-down menu.
 6. Click **Update volume type** to confirm.
 
-    The Database Instance goes into the `Initializing` state and remains available during the process. The time it takes to complete the process may vary, depending on the size of the volume.
+    The Database Instance goes into the `Initializing` state.
 
-### The volume changing process
+
+## The volume changing process
 
 During the process:
 
@@ -55,15 +57,3 @@ During the process:
     </Message>
 - When all the data is synchronized, a switchover is performed between nodes of the cluster. This means that the database will be unavailable few dozen of seconds during at this time.
 
-## How to increase a Block Storage volume
-
-1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays.
-2. Select the geographical region of the Instance you want to manage from the drop-down.
-3. Click the name of the Database Instance you want to configure. The Database Instance overview page displays.
-4. Scroll down to **Volume settings**.
-5. Specify your volume capacity (in GB). The amount you define will be your new volume capacity.
-     <Message type="important">
-      - You can increase your Block Storage volume to up to 10 TB.
-      - Block volume sizes cannot be decreased.
-    </Message>
-6. Click **Increase volume size** to confirm.