Skip to content

Commit 62c8dbb

Browse files
fix(rbd): my review
1 parent 3fb2e04 commit 62c8dbb

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -56,15 +56,15 @@ A [snapshot](/managed-databases/postgresql-and-mysql/how-to/manage-snapshots/) i
5656
## Encryption at rest
5757

5858
<Message type="important">
59-
Once activated on an instance, encryption at rest cannot be disabled.
59+
Once activated on a Database Instance, encryption at rest cannot be disabled.
6060
</Message>
6161

6262
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). At Scaleway `aes-xts-plain64` is used as the default. The management of the encryption key is done by Scaleway.
6363

6464
All databases, data (including logs), and snapshots will be encrypted. Logical backup encryption is not currently available.
6565

6666
<Message type="note">
67-
Encryption at rest can be activated after database instance creation via the [instance upgrade endpoint](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/#path-database-instances-upgrade-a-database-instance).
67+
Encryption at rest can be activated after Database Instance creation via the [upgrade endpoint](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/#path-database-instances-upgrade-a-database-instance).
6868
</Message>
6969

7070
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.

managed-databases/postgresql-and-mysql/how-to/create-a-database.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,11 +38,11 @@ Compared to traditional database management, which requires customers to provide
3838
</Message>
3939
- Enable [encryption at rest](/managed-databases/postgresql-and-mysql/concepts/#encryption-at-rest) if you want to ensure the permanent encryption of your database data.
4040
<Message type="important">
41-
Once activated on an instance, encryption at rest cannot be disabled.
41+
Once activated on a Database Instance, encryption at rest cannot be disabled.
4242
<br /><br />
4343
All databases, data (including logs), and snapshots will be encrypted. Logical backup encryption is not currently available.
4444
<br /><br />
45-
Encryption at rest can be activated after database instance creation via the [instance upgrade endpoint](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/#path-database-instances-upgrade-a-database-instance).
45+
Encryption at rest can be activated after Database Instance creation via the [upgrade endpoint](https://www.scaleway.com/en/developers/api/managed-database-postgre-mysql/#path-database-instances-upgrade-a-database-instance).
4646
<br /><br />
4747
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.
4848
</Message>

0 commit comments

Comments
 (0)