Skip to content

Commit 7c67595

Browse files
docs(rdb): add encryption activation on existing instances int-add-rdb (#3936)
1 parent e85205a commit 7c67595

File tree

2 files changed

+12
-4
lines changed

2 files changed

+12
-4
lines changed

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

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,11 +55,17 @@ A [snapshot](/managed-databases/postgresql-and-mysql/how-to/manage-snapshots/) i
5555

5656
## Encryption at rest
5757

58+
<Message type="important">
59+
Once activated on a Database Instance, encryption at rest cannot be disabled.
60+
</Message>
61+
5862
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.
5963

60-
When you enable encryption at rest, you cannot disable it after database creation. All databases, data (including logs), and snapshots will be encrypted. Logical backup encryption is not currently available.
64+
All databases, data (including logs), and snapshots will be encrypted. Logical backup encryption is not currently available.
6165

62-
During the beta phase, you can enable encryption on an existing Database Instance by opening a request via a [support ticket](https://console.scaleway.com/support).
66+
<Message type="note">
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).
68+
</Message>
6369

6470
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.
6571

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

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,9 +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-
When you enable encryption at rest, you cannot disable it after database creation. All databases, data (including logs), and snapshots will be encrypted. Logical backup encryption is not currently available.
41+
Once activated on a Database Instance, encryption at rest cannot be disabled.
4242
<br /><br />
43-
During the beta phase, you can enable encryption on an existing Database Instance by opening a request via a [support ticket](https://console.scaleway.com/support).
43+
All databases, data (including logs), and snapshots will be encrypted. Logical backup encryption is not currently available.
44+
<br /><br />
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).
4446
<br /><br />
4547
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.
4648
</Message>

0 commit comments

Comments
 (0)