Skip to content

Commit f091e73

Browse files
fix(rdb): triangle
1 parent ac3fbeb commit f091e73

File tree

5 files changed

+14
-4
lines changed

5 files changed

+14
-4
lines changed

pages/managed-databases-for-postgresql-and-mysql/api-cli/setting-up-encryption-at-rest.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ dates:
77
posted: 2024-12-19
88
---
99

10-
Encryption at rest allows you to permanently encrypt your database data. The data is encrypted at volume level using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup). The management of the encryption key is done by Scaleway.
10+
[Encryption at rest](/managed-databases-for-postgresql-and-mysql/concepts/#encryption-at-rest) allows you to permanently encrypt your database data. The data is encrypted at volume level using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup). The management of the encryption key is done by Scaleway.
1111

1212
The feature can be activated upon Database Instance creation via the console and the API, or after creation exclusively through the API with the [upgrade endpoint](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/#path-database-instances-upgrade-a-database-instance).
1313

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

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,8 @@ A Database Instance is a managed database service created upon a custom base ima
4040

4141
A [snapshot](/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots/) is a consistent, instantaneous copy of the Block Storage volume of your Database Instance at a certain point in time. They are designed to recover your data in case of failure or accidental alterations of the data by a user. They allow you to quickly create a new Instance from a previous state of your database, regardless of the size of the volume. Their limitation is that, unlike backups, snapshots can only be stored in the same location as the original data.
4242

43+
Refer to the [How to manage snapshots](/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots/) documentation page for more information.
44+
4345
## Encryption at rest
4446

4547
<Message type="important">
@@ -56,6 +58,8 @@ Encryption at rest can be activated after Database Instance creation via the [up
5658

5759
Enabling encryption means your database data will be copied into a new, encrypted block volume. This takes approximately 1 hour per 100 GB of storage. When switching volumes, expect a few seconds of downtime towards the end of the copying process.
5860

61+
Refer to the [Encryption at rest performance benchmark](/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots/) reference page to find a benchmark of the performance of Scaleway Managed Databases performing encryption at rest.
62+
s
5963

6064
## Endpoint
6165

@@ -65,6 +69,9 @@ A point of connection to a database. The endpoint is associated with an IPv4 add
6569

6670
A database engine is the software component that stores and retrieves your data from a database. Currently, PostgreSQL versions 9.6, 10, 11, 12, 13, 14, and 15 are available. MySQL is available in version 8.
6771

72+
Refer to the [PostgreSQL version updates](/managed-databases-for-postgresql-and-mysql/reference-content/pg-version-updates/) reference page for a list of PostreSQL version updates and the corresponding features that are supported at Scaleway.
73+
74+
6875
## High availability
6976

7077
Is a Database Instance configuration that allows you to create a standby node, with an up-to-date replica of the database. If the main node fails for any reason, the standby can take over requests, reducing downtime.
@@ -99,6 +106,9 @@ Compared to traditional database management, which requires customers to provisi
99106

100107
A Read Replica is a live copy of a Database Instance that behaves like an Instance, but that only allows read-only connections. The replica mirrors the data of the primary Database node and any changes made are synchronized and reflected in the replica.
101108

109+
Refer to the [How to manage Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas/) documentation page for more information.
110+
111+
102112
## Region and Availability Zone
103113

104114
<RegionAndAz />

pages/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ import Requirements from '@macros/iam/requirements.mdx'
1010

1111
A Read Replica is a live copy of a Database Instance that behaves like an Instance, but that only allows read-only connections. The replica mirrors the data of the primary Database node and any changes made are replicated to the replica asynchronously.
1212

13-
Read Replicas allow you to scale your Database Instance for read-heavy database workloads. They can also be used for business intelligence workloads.
13+
[Read Replicas](/managed-databases-for-postgresql-and-mysql/concepts/#read-replica) allow you to scale your Database Instance for read-heavy database workloads. They can also be used for business intelligence workloads.
1414

1515
<Requirements />
1616

pages/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ dates:
99
import Requirements from '@macros/iam/requirements.mdx'
1010
import Autobackups from '@macros/databases/autobackups.mdx'
1111

12-
[Snapshots](/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots/) allow you to restore data in a new Database Instance, instead of creating individual automated database backups. It is only available for Database Instances that use Block Storage volumes.
12+
[Snapshots](/managed-databases-for-postgresql-and-mysql/concepts/#database-snapshot) allow you to restore data in a new Database Instance, instead of creating individual automated database backups. It is only available for Database Instances that use Block Storage volumes.
1313

1414
When you set up [autobackups](/managed-databases-for-postgresql-and-mysql/how-to/manage-backups/) for Database Instances that use Block Storage, the automatic backups are created in snapshot format.
1515

pages/managed-databases-for-postgresql-and-mysql/reference-content/encryption-at-rest-performance-benchmark.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ dates:
77
posted: 2024-12-19
88
---
99

10-
In December 2024, the Scaleway Managed Databases team ran tests on DB-POP2-4C-16G Instances in a Private Network using `pgbench`. Several workloads (including read, oltp and large loads) were simulated with several scale factors (from 1M rows to 200M rows) and concurrent database connections set to 10. They measured the impact of encryption at rest on transactions, per second and latency.
10+
In December 2024, the Scaleway Managed Databases team ran tests on DB-POP2-4C-16G Instances in a Private Network using `pgbench`. Several workloads (including read, oltp and large loads) were simulated with several scale factors (from 1M rows to 200M rows) and concurrent database connections set to 10. They measured the impact of [encryption at rest](/managed-databases-for-postgresql-and-mysql/concepts/#encryption-at-rest) on transactions, per second and latency.
1111

1212
<Message type="important">
1313
For more information on pgbench transactions, refer to the "What is the 'Transaction' actually performed in pgbench?" section of the official [pgbench documentation](https://www.postgresql.org/docs/current/pgbench.html).

0 commit comments

Comments
 (0)