You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/managed-databases-for-postgresql-and-mysql/api-cli/setting-up-encryption-at-rest.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ dates:
7
7
posted: 2024-12-19
8
8
---
9
9
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.
11
11
12
12
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).
Copy file name to clipboardExpand all lines: pages/managed-databases-for-postgresql-and-mysql/concepts.mdx
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,6 +40,8 @@ A Database Instance is a managed database service created upon a custom base ima
40
40
41
41
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.
42
42
43
+
Refer to the [How to manage snapshots](/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots/) documentation page for more information.
44
+
43
45
## Encryption at rest
44
46
45
47
<Messagetype="important">
@@ -56,6 +58,8 @@ Encryption at rest can be activated after Database Instance creation via the [up
56
58
57
59
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.
58
60
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
59
63
60
64
## Endpoint
61
65
@@ -65,6 +69,9 @@ A point of connection to a database. The endpoint is associated with an IPv4 add
65
69
66
70
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.
67
71
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
+
68
75
## High availability
69
76
70
77
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
99
106
100
107
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.
101
108
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.
Copy file name to clipboardExpand all lines: pages/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replicas.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ import Requirements from '@macros/iam/requirements.mdx'
10
10
11
11
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.
12
12
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.
[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.
13
13
14
14
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.
Copy file name to clipboardExpand all lines: pages/managed-databases-for-postgresql-and-mysql/reference-content/encryption-at-rest-performance-benchmark.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ dates:
7
7
posted: 2024-12-19
8
8
---
9
9
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.
11
11
12
12
<Messagetype="important">
13
13
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