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/create-read-replica/).
+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/).

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/create-read-replica/).
+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/).

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-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-instance/#how-to-connect-to-a-database-instance-through-a-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/create-read-replica/) documentation page.
+
+ For more information, refer to the [How to create Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/) documentation page.
 

pages/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup.mdx → macros/databases/autobackups.mdx

@@ -1,29 +1,17 @@
 ---
-title: How to enable autobackup for Databases
-description:  Instructions for enabling Autobackup for PostgreSQL and MySQL databases.
-tags: managed-dabatase autobackup database
-dates:
-  validation: 2025-07-15
-  posted: 2019-05-11
+macro: autobackups
 ---
-import Requirements from '@macros/iam/requirements.mdx'
 
 With the autobackup feature, the creation and management of your Database Instance backups is automated according to your backup schedule configuration.
 
 Two types of autobackups are available at Scaleway: [backups](/managed-databases-for-postgresql-and-mysql/concepts/#database-backup) and [snapshots](/managed-databases-for-postgresql-and-mysql/concepts/#database-snapshot).
 
-Backups are used when your Database Instance's storage option is a Local volume. Snapshots are available for Database Instances that use [Block Storage Legacy](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-legacy) and [Block Storage](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage) volumes.
+Backups are used when your Database Instance's storage option is a Local volume. Snapshots are available for Database Instances that use [Block Storage](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage) volumes.
 
 <Message type="important">
   Although they bear the same feature name, automated snapshots and automated backups are different in their design. If you have a Database Instance using Block Storage, it is only possible to use automated snapshots as autobackup.
 </Message>
 
-<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/)
-
 <Message type="note">
   - The autobackup feature is enabled by default upon the creation of an Instance. Simultaneously, a schedule policy is created. The default autobackup frequency is of 1 per day with a retention period of 7 days. You can change this in the Database Instance information page after Instance creation.
   - By default, the Database Instance creation date is used as the base timestamp for the automated backups. When you change the schedule configuration, the moment you validated the new configuration becomes the new base timestamp. For example, if at 8 a.m. on a Thursday you update the autobackup frequency to 24h, your next autobackup will be created at 8 a.m. on a Friday.
@@ -40,8 +28,4 @@ Backups are used when your Database Instance's storage option is a Local volume.
     <Message type="note">
       Although autobackup is enabled by default, you can select **Manual** in the **Choose a backup configuration** step of the Database Instance creation wizard to disable the feature before you create the Instance. You can also disable it after the Database Instance is ready.
     </Message>
-5. Configure the backup frequency and retention, then click <Icon name="validate" /> to confirm.
-
-You can follow our documentation to [restore](/managed-databases-for-postgresql-and-mysql/how-to/manage-manual-backups/#how-to-restore-backups) and [export](/managed-databases-for-postgresql-and-mysql/how-to/manage-manual-backups/#how-to-export-backups) your backups.
-
-For snapshots, you can follow the [how to restore snapshots](/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots/#how-to-create-a-database-instance-from-a-snapshot) procedure to create a Database Instance from a snapshot.
+5. Configure the backup frequency and retention, then click <Icon name="validate" /> to confirm.

menu/navigation.json

@@ -2118,57 +2118,41 @@
                     "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": "Add users",
-                    "slug": "add-users"
-                  },
-                  {
-                    "label": "Manage permissions",
-                    "slug": "manage-permissions"
-                  },
-                  {
-                    "label": "Manage allowed IPs",
-                    "slug": "manage-allowed-ip-addresses"
-                  },
-                  {
-                    "label": "Monitor Database Instances with Cockpit",
-                    "slug": "monitor-databases-cockpit"
+                    "label": "Manage users",
+                    "slug": "manage-users"
                   },
                   {
-                    "label": "Change the volume type",
-                    "slug": "change-volume-type"
+                    "label": "Manage volumes",
+                    "slug": "manage-volumes"
                   },
                   {
-                    "label": "Enable Autobackup",
-                    "slug": "enable-autobackup"
+                    "label": "Manage nodes",
+                    "slug": "manage-nodes"
                   },
                   {
-                    "label": "Manage manual backups",
-                    "slug": "manage-manual-backups"
+                    "label": "Manage backups",
+                    "slug": "manage-backups"
                   },
                   {
                     "label": "Manage snapshots",
                     "slug": "manage-snapshots"
                   },
                   {
-                    "label": "Clone a Database Instance",
-                    "slug": "clone-a-database-instance"
+                    "label": "Manage Read Replicas",
+                    "slug": "manage-read-replicas"
                   },
                   {
-                    "label": "Create Read Replicas",
-                    "slug": "create-read-replica"
+                    "label": "Clone a Database Instance",
+                    "slug": "clone-a-database-instance"
                   },
                   {
-                    "label": "Manage Read Replicas",
-                    "slug": "manage-read-replica"
+                    "label": "Manage allowed IPs",
+                    "slug": "manage-allowed-ip-addresses"
                   },
                   {
                     "label": "Configure advanced settings",
@@ -2179,17 +2163,13 @@
                     "slug": "renew-tls-certificate"
                   },
                   {
-                    "label": "Upgrade a Database Instance",
-                    "slug": "upgrade-a-database"
+                    "label": "Monitor Database Instances with Cockpit",
+                    "slug": "monitor-databases-cockpit"
                   },
                   {
-                    "label": "Upgrade Database Instance engine version",
+                    "label": "Upgrade Database Instance engine versions",
                     "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-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-instance/#how-to-connect-to-a-database-instance-through-a-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/add-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/manage-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/create-read-replica/).
+  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/).
 </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/create-read-replica/).
+You can use the [Read Replica feature](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/).
 
 ## 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/enable-autobackup), 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/manage-backups), 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/connect-database-instance.mdx

@@ -3,18 +3,22 @@ title: How to connect to a Database Instance
 description: Learn how to connect to your PostgreSQL and MySQL Database Instances.
 tags: postgresql mysql database-instance managed-database database
 dates:
-  validation: 2025-03-11
+  validation: 2025-07-08
   posted: 2023-02-16
 ---
 import Requirements from '@macros/iam/requirements.mdx'
+import SshBastion from '@macros/databases/ssh-bastion.mdx'
 
 
 <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 valid [API key](/iam/how-to/create-api-keys/)
 - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/)
 
+## How to connect to a Database Instance through the public network
+
 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.
@@ -37,4 +41,65 @@ import Requirements from '@macros/iam/requirements.mdx'
 
   You are now connected to your Managed Database.
 
+## How to connect to a Database Instance through a Private Network
+
+[Private Networks](/vpc/concepts/#private-networks) allows you to enhance the security of your system's architecture by isolating it from the internet.
+
+When using Private Networks, your application connects directly to your Database nodes without going through a Load Balancer.
+
+This improves performance by reducing the latency between your application and your database nodes. It also increases the security of your databases, as Instances in your Private Network can directly communicate with your Database Instance, without passing through the public internet.
+
+You can create new Database Instances to attach to your Private Network, or attach existing ones.
+
+<Message type="note">
+  Managed PostgreSQL and MySQL Database Instances created after July 28th 2025 are compatible with the [VPC routing](/vpc/concepts/#routing) feature, which allows you to connect one or more Database Instances in a Private Network to resources in other Private Networks of the same VPC. Maintenance scheduled for later in August 2025 will make all pre-existing Managed PostgreSQL and MySQL Database Instances compatible as well. Refer to the [How to manage routing](/vpc/how-to/manage-routing/) documentation page for more information about VPC routing.
+</Message>
+
+### How to attach a Database Instance to a Private Network
+
+<Message type="note">
+  You can only attach your Database Instance to one Private Network at a time.
+</Message>
+
+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. Scroll to the **Network** section.
+    <Message type="note">
+      Alternatively, you can follow the next steps from the **Private Networks** tab. Click **+ Attach to a Private Network** to open the configuration pop-up.
+    </Message>
+5. Click **Attach Private Network** next to **Private endpoint**. A pop-up appears.
+6. Choose whether to:
+    - Select and attach an existing Private Network and select the network from the drop-down list.
+        <Message type="important">
+          The Database Instance must be attached to a Private Network in the same region.
+        </Message>
+    - Create and attach a new Private Network and enter the name of the network in the form.
+        <Message type="important">
+          If you select this option, a Private Network with default settings will be created in the same region as your Database Instance. Do not use a TLD (e.g. dev, cloud) as a name, to avoid conflicts.
+        </Message>
+
+    <Message type="note">
+      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/OpenTofu.
+    </Message>
+7. Click **Attach to Private Network** to conclude.
+
+### How to connect to a Database Instance through a Public Gateway
+
+<SshBastion />
+
+### How to detach a Database Instance from a Private Network
+
+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. Click the **Private Networks** tabs. The Private Network configuration displays.
+5. Click <Icon name="unlink" /> next to the static IP that you want to unlink from your Database Instance.
+6. Click **Detach resource** to remove the Instance from your Private Network.
 
+<Message type="note">
+This action takes a few moments to complete. During this time, your Database Instance:
+  - remains available,
+  - goes into **Configuring** mode, and
+  - network configuration actions become unavailable
+</Message>