From bbc4829a2b6c10fc150a1ba6a3d50540496d987a Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Mon, 2 Jun 2025 11:32:54 +0200 Subject: [PATCH 1/2] fix(rbd): add regionalization changes to docs --- .../how-to/add-a-database.mdx | 11 ++-- .../how-to/add-users.mdx | 13 ++-- .../how-to/apply-maintenance.mdx | 7 ++- .../how-to/change-volume-type.mdx | 9 +-- .../how-to/clone-a-database-instance.mdx | 13 ++-- .../how-to/configure-advanced-settings.mdx | 5 +- .../how-to/connect-database-instance.mdx | 9 +-- .../connect-database-private-network.mdx | 20 ++++--- .../how-to/create-a-database.mdx | 7 ++- .../how-to/create-read-replica.mdx | 13 ++-- .../how-to/delete-a-database.mdx | 7 ++- .../how-to/delete-db.mdx | 9 +-- .../how-to/enable-autobackup.mdx | 7 ++- .../how-to/enable-high-availability.mdx | 9 +-- .../how-to/manage-allowed-ip-addresses.mdx | 9 +-- .../how-to/manage-permissions.mdx | 11 ++-- .../how-to/manage-read-replica.mdx | 60 ++++++++++--------- .../how-to/remove-public-endpoint.mdx | 18 +++--- .../how-to/renew-tls-certificate.mdx | 7 ++- .../how-to/upgrade-a-database.mdx | 20 ++++--- .../how-to/upgrade-version.mdx | 9 +-- .../quickstart.mdx | 27 +++++---- 22 files changed, 166 insertions(+), 134 deletions(-) diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/add-a-database.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/add-a-database.mdx index a4241e0771..a03e38b2a1 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/add-a-database.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/add-a-database.mdx @@ -20,10 +20,11 @@ categories: - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays. -2. Click the Database Instance name or > **More info** to access the Database Instance information page. -3. Go to the **Databases** tab. A list of your databases displays. The list includes the database created by default upon Database Instance creation. -4. Click **+ Create database** to create a new one. A pop-up appears. -5. Enter a name for your database. -6. Click **Create database** to confirm. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the Database Instance name or > **More info** to access the Database Instance information page. +4. Go to the **Databases** tab. A list of your databases displays. The list includes the database created by default upon Database Instance creation. +5. Click **+ Create database** to create a new one. A pop-up appears. +6. Enter a name for your database. +7. Click **Create database** to confirm. The new database appears in the list of your databases. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/add-users.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/add-users.mdx index 634001330f..6a9820efe8 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/add-users.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/add-users.mdx @@ -23,14 +23,15 @@ Users can connect to a database and access its data. Each one has a different se - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) 1. Click **PostgreSQL and MySQL** under **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. Go to the **Users** tab. A list of users displays. If it is the first time you create a user, your list will display the user you set up during the creation of your Database Instance. -4. Click **+ Create user** to create a new user, if you wish to. -5. Click to grant admin rights to the user. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the database name or > **More info** to access the Database Instance information page. +4. Go to the **Users** tab. A list of users displays. If it is the first time you create a user, your list will display the user you set up during the creation of your Database Instance. +5. Click **+ Create user** to create a new user, if you wish to. +6. Click to grant admin rights to the user. Admin rights allow a user to create logical databases and users. These right do not override the permissions configured for the logical databases. Logical database permissions must be set up in the Permissions tab. -6. Enter a **username** and **password**. +7. Enter a **username** and **password**. Optionally, you can configure the appropriate permissions according to the user. Three types of permissions are available: @@ -40,7 +41,7 @@ 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. -7. Click **Create user** to confirm. +8. Click **Create user** to confirm. Once the user is created, it is displayed in the user list. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/apply-maintenance.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/apply-maintenance.mdx index ccd71b161d..eee3f22649 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/apply-maintenance.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/apply-maintenance.mdx @@ -25,8 +25,9 @@ These maintenance operations are set up, run, and scheduled by Scaleway, but you - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) scheduled for maintenance 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays. -2. Look for an orange info icon to identify which Database Instances are scheduled for maintenance. -3. Click the Database Instance name or > **More info** to access the database information page. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Look for an orange info icon to identify which Database Instances are scheduled for maintenance. +4. Click the Database Instance name or > **More info** to access the database information page. If your Database Instance is scheduled for maintenance, you will see a banner on the top of the page informing you when the scheduled maintenance will take place. You can either wait for the maintenance to be applied automatically at the expected date and time, or you can apply it immediately. @@ -35,7 +36,7 @@ These maintenance operations are set up, run, and scheduled by Scaleway, but you -4. Click **Apply maintenance now** to apply the maintenance immediately. You are redirected to a screen that shows you the status of the maintenance. If you want a more detailed maintenance status, you can [use the API](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/#path-database-instances-apply-database-instance-maintenance). +5. Click **Apply maintenance now** to apply the maintenance immediately. You are redirected to a screen that shows you the status of the maintenance. If you want a more detailed maintenance status, you can [use the API](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/#path-database-instances-apply-database-instance-maintenance). Your Database Instance will be unavailable during the maintenance. This might take a few minutes. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type.mdx index 8fbc5da38b..fe4b5d3f33 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type.mdx @@ -23,16 +23,17 @@ It is possible to change your [volume type](/managed-databases-for-postgresql-an - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) with local Storage 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays. -2. Click the name of the Database Instance you want to edit. The database's Overview page displays. -3. Scroll down to **Volume settings**, then click **Change volume type**. +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 edit. The database's Overview page displays. +4. Scroll down to **Volume settings**, then click **Change volume type**. Before changing the volume type, make sure your Instance is in one of the following states: - `READY` (represented as "Running" in the Scaleway console) - `DISK_FULL` A pop-up appears. -4. Select **Block Storage** from the drop-down menu. -5. Click **Update volume type** to confirm. +5. Select **Block Storage** from the drop-down menu. +6. Click **Update volume type** to confirm. The Database Instance goes into the `Initializing` state. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/clone-a-database-instance.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/clone-a-database-instance.mdx index 77d6b02b29..ea8e974ae4 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/clone-a-database-instance.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/clone-a-database-instance.mdx @@ -29,17 +29,18 @@ The clone feature allows you to create a new Database Instance from an existing ## How to clone a Database Instance 1. Click **PostgreSQL and MySQL** under **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. Scroll down to the **Clone** section. -4. Click **Clone Database Instance**. A pop-up displays. -5. Enter a name for your database or leave the default name suggested by the Scaleway console. -6. Select a node type. You can keep the same node type, or upgrade to a bigger one. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the database name or > **More info** to access the Database Instance information page. +4. Scroll down to the **Clone** section. +5. Click **Clone Database Instance**. A pop-up displays. +6. Enter a name for your database or leave the default name suggested by the Scaleway console. +7. Select a node type. You can keep the same node type, or upgrade to a bigger one. If you have a new-generation Database Instance using a Local volume node type and want to upgrade to an Instance that uses Block volumes node type, you must [change the volume type](/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type/) to Block Storage first.

Similarly, if you have a new-generation Database Instance using a [Block volume](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage) and want to create a clone on a first-generation Instance, you must first change the volume type to [Block Storage Legacy](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-legacy). -7. Click **Clone Database Instance**. +8. Click **Clone Database Instance**. The source Database Instance remains available during the cloning process in **Backing up mode**. Some actions are not available during this time.

diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings.mdx index 45daba40c4..b367d1b3a0 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings.mdx @@ -27,8 +27,9 @@ Advanced settings allow you to modify the default configuration of your database 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays. -2. Click the Database Instance name or > **More info** to access the database information page. -3. Click the **Advanced settings** tab. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the Database Instance name or > **More info** to access the database information page. +4. Click the **Advanced settings** tab. To add advanced settings, follow these steps: diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx index e3c1f3a36b..ba67e205bb 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance.mdx @@ -21,12 +21,13 @@ categories: - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) 1. Click **PostgreSQL and MySQL** under **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. Retrieve the Database Instance IP and port from the Database Instance information section. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the database name or > **More info** to access the Database Instance information page. +4. 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 database client connection command. This already includes your database IP and port. -4. Connect to your database with the database client of your engine. +5. Connect to your database with the database client of your engine. For MySQL, run the following command: ```bash @@ -37,7 +38,7 @@ categories: ```bash psql -h -p -U -d rdb ``` -5. Enter the password that you defined upon [Database Instance creation](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/). +6. Enter the password that you defined upon [Database Instance creation](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/). You are now connected to your Managed Database. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network.mdx index 368802abc7..8c1190a678 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network.mdx @@ -36,13 +36,14 @@ You can create new Database Instances to attach to your Private Network, or atta 1. Click **PostgreSQL and MySQL** under **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. Scroll to the **Network** section. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the database name or > **More info** to access the Database Instance information page. +4. Scroll to the **Network** section. Alternatively, you can follow the next steps from the **Private Networks** tab. Click **+ Attach to a Private Network** to open the configuration pop-up. -4. Click **Attach Private Network** next to **Private endpoint**. A pop-up appears. -5. Choose whether to: +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. The Database Instance must be attached to a Private Network in the same region. @@ -55,7 +56,7 @@ You can create new Database Instances to attach to your Private Network, or atta 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. -6. Click **Attach to Private Network** to conclude. +7. Click **Attach to Private Network** to conclude. ## How to connect to a Database Instance through a Public Gateway @@ -64,10 +65,11 @@ You can create new Database Instances to attach to your Private Network, or atta ## 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. Click the database name or > **More info** to access the Database Instance information page. -3. Click the **Private Networks** tabs. The Private Network configuration displays. -4. Click next to the static IP that you want to unlink from your Database Instance. -5. Click **Detach resource** to remove the Instance from your Private Network. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the database name or > **More info** to access the Database Instance information page. +4. Click the **Private Networks** tabs. The Private Network configuration displays. +5. Click 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. This action takes a few moments to complete. During this time, your Database Instance: diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/create-a-database.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/create-a-database.mdx index 72e41a7b47..4a57f9b509 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/create-a-database.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/create-a-database.mdx @@ -26,8 +26,9 @@ Compared to traditional database management, which requires customers to provide - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. If you do not have a database already created, the creation page displays. -2. Click **Create Database Instance**. The creation wizard displays. -3. Complete the following steps in the wizard: +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click **Create Database Instance**. The creation wizard displays. +4. Complete the following steps in the wizard: - Select a database engine. **PostgreSQL** and **MySQL** are available. - Choose a region. This is the geographical location where your database will be deployed. - Select a database configuration. You can choose between: @@ -68,4 +69,4 @@ Compared to traditional database management, which requires customers to provide - one number - Enter a name for your Instance. -4. Click **Create Database Instance** to confirm your choices and launch creation. \ No newline at end of file +5. Click **Create Database Instance** to confirm your choices and launch creation. \ No newline at end of file diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica.mdx index eafa4f0f6f..be92b9ea2c 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica.mdx @@ -25,15 +25,16 @@ Read Replicas allow you to scale your Database Instance for read-heavy database - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) 1. Click **PostgreSQL and MySQL** under **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. Scroll down to the **Read Replica** section. -4. Click **Create Read Replica**. A pop-up displays. -5. Select the Availability Zone (AZ) configuration. Two configurations are available: +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the database name or > **More info** to access the Database Instance information page. +4. Scroll down to the **Read Replica** section. +5. Click **Create Read Replica**. A pop-up displays. +6. Select the Availability Zone (AZ) configuration. Two configurations are available: - **Same AZ**: Your Read Replica is hosted in the same AZ as your main Database Instance. We recommend this option for low-latency workflows. - **Multi-AZ**: Your Read Replica is hosted in a different AZ, ensuring the resilience of your Replica. We recommend this option for ensuring the availability of your infrastructure, and improving your disaster recovery plan. -6. Select the network type. Two types are available: +7. Select the network type. Two types are available: - **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 in the Allowed IPs section. - **Private Networks** - Private Networks allow you to create virtual Private Networks for your Databases, enabling them to communicate in an isolated network without the need for a public IP address. If you select this option, you must select an existing Private Network to attach to your Read Replica. @@ -45,7 +46,7 @@ Read Replicas allow you to scale your Database Instance for read-heavy database If you select **Public network**, you can [attach a Private Network](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replica/#how-to-manage-private-networks) to your Read Replica after its creation. If you choose to attach your Read Replica to a Private Network, you will not be able to add a Public Network to the same Read Replica later via the Scaleway console. You can, however, use the [Managed Databases API](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/) to do so via a command line or Terraform/OpenTofu. -7. Click **Create Read Replica**. A list of your Read Replicas displays. +8. Click **Create Read Replica**. A list of your Read Replicas displays. Read Replicas have the same node types as the main node. For example, if your main node is of the DB-GP-S type, so is your Read Replica. The Replica also inherits the main node's configuration. The data of your main node is fully replicated in the Read Replica. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/delete-a-database.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/delete-a-database.mdx index 7b170ca041..471cde212d 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/delete-a-database.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/delete-a-database.mdx @@ -21,12 +21,13 @@ categories: - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) 1. Click **PostgreSQL and MySQL** under **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. Scroll down the page to the **Delete Database Instance** section and click **Delete Database Instance**. A pop-up appears to inform that: +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the database name or > **More info** to access the Database Instance information page. +4. Scroll down the page to the **Delete Database Instance** section and click **Delete Database Instance**. A pop-up appears to inform that: This will permanently destroy your Instance, and all your data will be lost. This action is irreversible. -4. Type **DELETE** to confirm and click **Delete Database Instance**. +5. Type **DELETE** to confirm and click **Delete Database Instance**. Alternatively, you can delete your Instance from your Database Instances list by clicking next to the Instance name and then **Delete**. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/delete-db.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/delete-db.mdx index 6f135f14ef..eefe5f162b 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/delete-db.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/delete-db.mdx @@ -21,10 +21,11 @@ categories: - A [database](/managed-databases-for-postgresql-and-mysql/how-to/add-a-database/) 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays. -2. Click the Database Instance name or > **More info** to access the Database Instance information page. -3. Go to the **Databases** tab. A list of your databases displays. -4. Click > **Delete** next to the database of your choice. A pop-up appears to inform that: +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the Database Instance name or > **More info** to access the Database Instance information page. +4. Go to the **Databases** tab. A list of your databases displays. +5. Click > **Delete** next to the database of your choice. A pop-up appears to inform that: This will permanently destroy your Instance, and all your data will be lost. This action is irreversible. -5. Type **DELETE** to confirm and click **Delete database**. \ No newline at end of file +6. Type **DELETE** to confirm and click **Delete database**. \ No newline at end of file diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup.mdx index 2419b34167..61b76565ec 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup.mdx @@ -39,15 +39,16 @@ Backups are used when your Database Instance's storage option is a Local volume. 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays. -2. Click the Database Instance name or > **More info** to access the Database Instance's Overview page. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the Database Instance name or > **More info** to access the Database Instance's Overview page. If you have a Database Instance using Block Storage, you can follow the next steps from the **Snapshots** tab. -3. Scroll down to **Backup configuration** and click . +4. Scroll down to **Backup configuration** and click . 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. -4. Configure the backup frequency and retention, then click to confirm. +5. Configure the backup frequency and retention, then click 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. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-high-availability.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-high-availability.mdx index 6cd5a1d03f..c9758d3a06 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-high-availability.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-high-availability.mdx @@ -32,10 +32,11 @@ If you are standalone mode, you can change the node configuration to High Availa - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) in standalone mode. 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays. -2. Click the name of the Database Instance you want to configure. Your database's **Overview** page displays. -3. Scroll down to the **Node settings** section. Then, click **Activate High Availability**. -4. Review the new estimated cost. -5. Click **Activate**. +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. Your database's **Overview** page displays. +4. Scroll down to the **Node settings** section. Then, click **Activate High Availability**. +5. Review the new estimated cost. +6. Click **Activate**. The action of changing the node configuration will perform a rolling upgrade of your Database Instance. During this process, the Database Instance will be unavailable for several tens of seconds. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-allowed-ip-addresses.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-allowed-ip-addresses.mdx index d06e6c90e9..cb8f0f6bdd 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-allowed-ip-addresses.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-allowed-ip-addresses.mdx @@ -29,13 +29,14 @@ Allowed IPs define remote access restrictions for your Database Instance. The de ## How to add an IP address 1. Click **PostgreSQL and MySQL** in the **Databases** section of the [Scaleway console](https://console.scaleway.com) side menu. A list of your Database Instances displays. -2. Click the database name or > **More info** to access the database information page. -3. Click **Allowed IPs** tab. A list of your allowed IP addresses displays. -4. Click **Add allowed IP**. The IP can be a single IP or an IP block. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the database name or > **More info** to access the database information page. +4. Click **Allowed IPs** tab. A list of your allowed IP addresses displays. +5. Click **Add allowed IP**. The IP can be a single IP or an IP block. The IP must be specified in CIDR format, i.e. `198.51.100.135/32` for a single IP or `198.51.100.0/24` for an IP block. -5. Enter a single IP address or a subnetwork. +6. Enter a single IP address or a subnetwork. To restore initial settings and allow connections from all IPs, add the following IP block to the list: `0.0.0.0/0`. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-permissions.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-permissions.mdx index ebb65102de..9334a13b9a 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-permissions.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-permissions.mdx @@ -25,10 +25,11 @@ Permissions define the actions a user can perform on a logical database. A datab ## Set permissions for an existing user 1. Click **PostgreSQL and MySQL** under **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. Go to the **Users** tab. A list of users displays. -4. Click > **Update permissions** to open the user permissions panel. -5. Select the appropriate permissions for each database. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the database name or > **More info** to access the Database Instance information page. +4. Go to the **Users** tab. A list of users displays. +5. Click > **Update permissions** to open the user permissions panel. +6. Select the appropriate permissions for each database. Three types of permissions are available: - **None:** No access to the database @@ -36,7 +37,7 @@ Permissions define the actions a user can perform on a logical database. A datab - **Write:** Allow users to write content in databases -6. Click **Update user** to confirm. +7. Click **Update user** to confirm. ## Set permissions for a new user diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replica.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replica.mdx index 56e0fb9015..970d739138 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replica.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replica.mdx @@ -26,10 +26,11 @@ categories: When you resync a Read Replica, first it is reset, and then its data is resynchronized from the primary node. Your Read Replica will be unavailable during the resync process. The duration of this process is proportional to your Database Instance size. The configured endpoints will not change. 1. Click **PostgreSQL and MySQL** under **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. Scroll down to the **Read Replica** section. -4. Click > **Resync** next to the name of the Read Replica you want to resync. A pop-up displays. -5. Make sure you have selected the correct Read Replica and click **Resync**. The list of your Read Replicas displays. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the database name or > **More info** to access the Database Instance information page. +4. Scroll down to the **Read Replica** section. +5. Click > **Resync** next to the name of the Read Replica you want to resync. A pop-up displays. +6. Make sure you have selected the correct Read Replica and click **Resync**. The list of your Read Replicas displays. Your Read Replica will be unavailable during the resync process. The duration of this process is proportional to your Database Instance size. The configured endpoints will not change. @@ -40,9 +41,10 @@ When you resync a Read Replica, first it is reset, and then its data is resynchr It is possible to promote a Read Replica node to a standalone Database Instance. 1. Click **PostgreSQL and MySQL** under **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. Scroll down to the **Read Replica** section. -4. Click > **Promote Read Replica** next to the name of the Read Replica you want to promote. A pop-up displays. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the database name or > **More info** to access the Database Instance information page. +4. Scroll down to the **Read Replica** section. +5. Click > **Promote Read Replica** next to the name of the Read Replica you want to promote. A pop-up displays. Promoting a Read Replica is irreversible. Make sure that the main Database Instance node has completed all ongoing operations, and that the Read Replica lag is down to zero before promoting it. This helps ensure that the promoted Read Replica contains all operations from the main node. @@ -50,8 +52,8 @@ It is possible to promote a Read Replica node to a standalone Database Instance. If the Read Replica you promote is attached to a Private Network, the resulting node will also be attached to the same Private Network. It will maintain the same private endpoint. -5. Click **Promote Read Replica**. -6. Go back to the list of your Database Instances. The promoted Read Replica appears. +6. Click **Promote Read Replica**. +7. Go back to the list of your Database Instances. The promoted Read Replica appears. The new Instance originating from the Read Replica promotion will bear the prefix `promoted`, followed by the name of the original Database Instance that was replicated. You can change the name of your Database Instance on its overview page anytime. To do so, click next to its name. @@ -63,36 +65,39 @@ You can attach and detach your Read Replica to a Private Network even after its ### Attach your Read Replica to a new Private Network 1. Click **PostgreSQL and MySQL** under **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. Scroll down to the **Read Replica** section. -4. Click > **Attach Private Network** next to the name of your selected Read Replica. A pop-up displays. -5. Select **Create and attach a new Private Network**. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the database name or > **More info** to access the Database Instance information page. +4. Scroll down to the **Read Replica** section. +5. Click > **Attach Private Network** next to the name of your selected Read Replica. A pop-up displays. +6. Select **Create and attach a new Private Network**. 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. -6. Click **Attach Private Network**. +7. Click **Attach Private Network**. ### Attach your Read Replica to an existing Private Network 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays. -2. Click the Database Instance name or > **More info** to access the Database Instance information page. -3. Scroll down to the **Read Replica** section. -4. Click > **Attach Private Network** next to the name of your selected Read Replica. A pop-up displays. -5. Select an existing Private Network to attach to your Read Replica. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the Database Instance name or > **More info** to access the Database Instance information page. +4. Scroll down to the **Read Replica** section. +5. Click > **Attach Private Network** next to the name of your selected Read Replica. A pop-up displays. +6. Select an existing Private Network to attach to your Read Replica. 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. -6. Click **Attach to Private Network** to confirm. +7. Click **Attach to Private Network** to confirm. ### Detach your Read Replica from a Private Network If you already have an attached Private Network, you can detach it from your Read Replica. 1. Click **PostgreSQL and MySQL** under **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. Scroll down to the **Read Replica** section. -4. Click > **Detach Private Network** next to the name of your selected Read Replica. A pop-up displays to ask if you are sure you want to detach the Private Network. -5. Click **Detach Private Network** to proceed. The list of your Read Replicas displays. The private endpoint is removed. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the database name or > **More info** to access the Database Instance information page. +4. Scroll down to the **Read Replica** section. +5. Click > **Detach Private Network** next to the name of your selected Read Replica. A pop-up displays to ask if you are sure you want to detach the Private Network. +6. Click **Detach Private Network** to proceed. The list of your Read Replicas displays. The private endpoint is removed. ## How to delete a public endpoint @@ -101,12 +106,13 @@ Refer to the [How to delete a public endpoint](/managed-databases-for-postgresql ## How to delete Read Replicas 1. Click **PostgreSQL and MySQL** under **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. Scroll down to the **Read Replica** section. -4. Click > **Delete**. A pop-up appears. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the database name or > **More info** to access the Database Instance information page. +4. Scroll down to the **Read Replica** section. +5. Click > **Delete**. A pop-up appears. This is an irreversible that action permanently deletes your Read Replica and all its associated endpoints. -5. Click **Delete Read Replica** to do so. The list of your Read Replicas displays. +6. Click **Delete Read Replica** to do so. The list of your Read Replicas displays. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/remove-public-endpoint.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/remove-public-endpoint.mdx index 406a0813f0..3e964ecab7 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/remove-public-endpoint.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/remove-public-endpoint.mdx @@ -28,13 +28,14 @@ If you are using a public endpoint with your Database Instances or Read Replicas ## From Database Instances 1. Click **PostgreSQL and MySQL** under **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. Scroll to the **Network** section. -4. Click **Remove** next to **Public endpoint**. A pop-up appears. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the database name or > **More info** to access the Database Instance information page. +4. Scroll to the **Network** section. +5. Click **Remove** next to **Public endpoint**. A pop-up appears. When you remove a public endpoint, your Database Instance becomes inaccessible over the internet. -5. Click **Remove public endpoint** to do so. +6. Click **Remove public endpoint** to do so. Your Database Instance re-initializes. @@ -50,13 +51,14 @@ If you are using a public endpoint with your Database Instances or Read Replicas - A [Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/) 1. Click **PostgreSQL and MySQL** under **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. Scroll down to the **Read Replica** section. -4. Click > **Remove public endpoint**. A pop-up appears. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the database name or > **More info** to access the Database Instance information page. +4. Scroll down to the **Read Replica** section. +5. Click > **Remove public endpoint**. A pop-up appears. When you remove a public endpoint, your Read Replica becomes inaccessible over the internet. -5. Click **Remove public endpoint** to do so. +6. Click **Remove public endpoint** to do so. Your Read Replica re-initializes. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/renew-tls-certificate.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/renew-tls-certificate.mdx index 6bd6dc12dd..dd7950cac0 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/renew-tls-certificate.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/renew-tls-certificate.mdx @@ -25,9 +25,10 @@ A certificate is generated automatically upon the creation of a Database Instanc - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) 1. Click **PostgreSQL and MySQL** under **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 **Renew** under **TLS Certificate** in the **Database Instance Information** section. A pop-up appears. -4. Click **Renew TLS certificate** once you have read the warnings displayed and wish to continue. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the database name or > **More info** to access the Database Instance information page. +4. Click **Renew** under **TLS Certificate** in the **Database Instance Information** section. A pop-up appears. +5. Click **Renew TLS certificate** once you have read the warnings displayed and wish to continue. Renewing a certificate means you: diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-a-database.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-a-database.mdx index 9f335f05a6..562f204475 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-a-database.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-a-database.mdx @@ -25,14 +25,15 @@ You can upgrade your Database Instances in two ways: by increasing its Block Sto ## 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. Click the name of the Database Instance you want to configure. The Database Instance overview page displays. -3. Scroll down to **Volume settings**. -4. Specify your volume capacity (in GB). The amount you define will be your new volume capacity. - +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. + - You can increase your Block Storage volume to up to 10 TB. - Block volume sizes cannot be decreased. -5. Click **Increase volume size** to confirm. +6. Click **Increase volume size** to confirm. ## How to change the node type @@ -43,10 +44,11 @@ You can upgrade your Database Instances in two ways: by increasing its Block Sto 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays. -2. Click the name of the Database Instance you want to configure. Your database's Overview page displays. -3. Scroll down to the **Node settings** section. Then, click **Change node type**. -4. Choose the specifications of the new Database Instance from the drop-down list. -5. Click **Update node type** to confirm your choices. +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. Your database's Overview page displays. +4. Scroll down to the **Node settings** section. Then, click **Change node type**. +5. Choose the specifications of the new Database Instance from the drop-down list. +6. Click **Update node type** to confirm your choices. Make sure that the Database Instance you choose provides sufficient disk space for your database. Otherwise, an error message will be displayed, and the database will not be upgraded. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx index ed8bb728fd..dcfe23305c 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx @@ -59,10 +59,11 @@ We recommend you remove the identified instances before continuing. ## How to upgrade the engine version 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu. A list of your Database Instances displays. -2. Click the name of the database whose engine you want to upgrade. The Database Instance information page appears. -3. Click **Upgrade** under **Database engine**. A pop-up appears. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the name of the database whose engine you want to upgrade. The Database Instance information page appears. +4. Click **Upgrade** under **Database engine**. A pop-up appears. -3. Select the upgrade method. Two methods are available: +5. Select the upgrade method. Two methods are available: - **Upgrade only**: This method has no impact on your original Database Instance. Your Database Instance will remain available with its original endpoint and will continue to be billed. - **Upgrade and switch incoming traffic**: With this method, your endpoint is migrated to the new Database Instance automatically. This option will create a clone of your Database Instance, and will automatically migrate the endpoint to the new Instance. The original Database Instance remains available and will continue to be billed. The endpoint will be deleted from the original Database Instance. @@ -78,7 +79,7 @@ We recommend you remove the identified instances before continuing. - Run the migration without checking the "migration endpoint" flag. If the test is successful, you can then proceed with the actual migration. Follow the [migrating endpoints via the CLI](/managed-databases-for-postgresql-and-mysql/api-cli/migrating-endpoints/) procedure to migrate your endpoints after the upgrade. You can use the same CLI command to revert the endpoint migration anytime. - Keep in mind that reverting the endpoint will not affect the data stored on the databases. This means that if some entries were added to the upgraded database, they will not be added back to the old version when you change the endpoints. -4. Click **Upgrade version**. A new Database Instance is created. +5. Click **Upgrade version**. A new Database Instance is created. - In PostgreSQL major upgrades, the `pgaudit` and `pg_stat_statements` [engine extensions](/managed-databases-for-postgresql-and-mysql/reference-content/postgresql-extensions) will be removed. You must reinstall these extensions on each database they are installed once the upgrade is complete. diff --git a/pages/managed-databases-for-postgresql-and-mysql/quickstart.mdx b/pages/managed-databases-for-postgresql-and-mysql/quickstart.mdx index c6b0126c3d..02994770ec 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/quickstart.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/quickstart.mdx @@ -32,8 +32,9 @@ Discover the Managed Database for PostgreSQL and MySQL interface in the Scaleway ## How to create a database 1. Click **PostgreSQL and MySQL** under **Databases** on the side menu, if you do not have a Database Instance already created, the creation page displays. -2. Click **Create Database Instance**. The creation wizard displays. -3. Complete the following steps in the wizard: +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click **Create Database Instance**. The creation wizard displays. +4. Complete the following steps in the wizard: - Select a database engine. **PostgreSQL** and **MySQL** are available. - Choose a region. This is the geographical location where your database will be deployed. - Select a database configuration. You can choose between: @@ -61,7 +62,7 @@ Discover the Managed Database for PostgreSQL and MySQL interface in the Scaleway - one number - Enter a name for your Instance. -4. Click **Create Database Instance** to confirm your choices and launch creation. +5. Click **Create Database Instance** to confirm your choices and launch creation. You are taken to the **Overview** tab for your database, where you can see information including the **Endpoint** to enable you to connect to your database. @@ -69,14 +70,15 @@ Discover the Managed Database for PostgreSQL and MySQL interface in the Scaleway ## How to add users 1. Click **PostgreSQL and MySQL** under **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. Go to the **Users** tab. A list of users displays. If it is the first time you create a user, your list will display the user you set up during the creation of your Database Instance. -4. Click **+ Create user** to create a new user, if you wish to. -5. Click to grant admin rights to the user. +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the database name or > **More info** to access the Database Instance information page. +4. Go to the **Users** tab. A list of users displays. If it is the first time you create a user, your list will display the user you set up during the creation of your Database Instance. +5. Click **+ Create user** to create a new user, if you wish to. +6. Click to grant admin rights to the user. Admin rights allow a user to create logical databases and users. These rights do not override the permissions configured for the logical databases. Logical database permissions must be set up in the **Permissions** tab. -6. Enter a **username** and **password**. +7. Enter a **username** and **password**. Optionally, you can configure the appropriate permissions according to the user. Three types of permissions are available: @@ -85,7 +87,7 @@ Discover the Managed Database for PostgreSQL and MySQL interface in the Scaleway - **Write:** Allow users to write content in databases You can select the permission type in the Permissions tab. -7. Click **Create user** to confirm. +8. Click **Create user** to confirm. Once the user is created, it is displayed in the user list. @@ -94,12 +96,13 @@ To update the password or permissions, or delete the user, click > **More info** to access the Database Instance 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: +2. Select the geographical region of the Instance you want to manage from the drop-down. +3. Click the database name or > **More info** to access the Database Instance information page. +4. Scroll down the page to the **Delete Database Instance** section and click **Delete Database Instance**. A pop-up appears to inform that: This action is irreversible and will permanently delete this Database Instance and all its associated data. -4. Type **DELETE** to confirm and click **Delete Database Instance**. +5. Type **DELETE** to confirm and click **Delete Database Instance**. Alternatively, you can delete your Instance from your Database Instances list by clicking next to the Instance name and then **Delete**. \ No newline at end of file From 2e8cd5714acddbbd9fea1fc01124fdaeff8b4e75 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Mon, 2 Jun 2025 17:17:39 +0200 Subject: [PATCH 2/2] fix(rdb): review jess Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com> --- .../how-to/upgrade-version.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx index dcfe23305c..fee9b9acea 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx @@ -79,7 +79,7 @@ We recommend you remove the identified instances before continuing. - Run the migration without checking the "migration endpoint" flag. If the test is successful, you can then proceed with the actual migration. Follow the [migrating endpoints via the CLI](/managed-databases-for-postgresql-and-mysql/api-cli/migrating-endpoints/) procedure to migrate your endpoints after the upgrade. You can use the same CLI command to revert the endpoint migration anytime. - Keep in mind that reverting the endpoint will not affect the data stored on the databases. This means that if some entries were added to the upgraded database, they will not be added back to the old version when you change the endpoints. -5. Click **Upgrade version**. A new Database Instance is created. +6. Click **Upgrade version**. A new Database Instance is created. - In PostgreSQL major upgrades, the `pgaudit` and `pg_stat_statements` [engine extensions](/managed-databases-for-postgresql-and-mysql/reference-content/postgresql-extensions) will be removed. You must reinstall these extensions on each database they are installed once the upgrade is complete.