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
Recommendations for preparing storage for Databend deployments.
4
+
description: Recommendations for preparing storage for Databend deployments.
6
5
---
7
6
8
7
This topic explains the recommended storage configurations for deploying Databend in production environments.
9
8
10
-
11
9
## AWS S3
12
10
13
11
When deploying Databend with AWS S3 in production environments, consider the following recommendations:
14
12
15
-
16
13
### Security
17
14
18
15
Block public access to your S3 bucket to prevent unauthorized access to your data. You can configure the following settings to restrict public access:
19
16
20
17
Go to the AWS Management Console, select the S3 service, enter the bucket name, and click on the **Permissions** tab. Under the **Block public access** section, click **Edit**, then select the **Block all public access** option and click **Save**.
21
18
22
-
23
19
### Encryption
24
20
25
21
Enable server-side encryption on your S3 bucket to protect your data at rest. You can choose from the following encryption options:
@@ -29,24 +25,37 @@ Enable server-side encryption on your S3 bucket to protect your data at rest. Yo
29
25
30
26
Go to the AWS Management Console, select the S3 service, enter the bucket name, and click on the **Properties** tab. Under the **Default encryption** section, click **Edit**, then select the encryption option and click **Save**.
31
27
32
-
33
28
### Bucket Versioning
34
29
35
30
Enable versioning on your S3 bucket to protect against accidental deletion of objects. Versioning allows you to recover objects from accidental deletion or overwrite.
36
31
37
32
Go to the AWS Management Console, select the S3 service, enter the bucket name, and click on the **Properties** tab. Under the **Versioning** section, click **Edit**, then select **Enable versioning** and click **Save**.
38
33
39
-
40
34
### Bucket Lifecycle Policies
41
35
42
36
Lifecyle rule is needed when Bucket Versioning is enabled. You can configure lifecycle policies to automatically delete old versions of objects or transition objects to different storage classes.
43
37
44
-
1. Go to the AWS Management Console, select the S3 service, enter the bucket name, and click on the **Management** tab. Under the **Lifecycle** section, click **Add lifecycle rule** to create a new rule.
38
+
- Configure lifecycle rule to delete old versions of objects.
39
+
40
+
1. Go to the AWS Management Console, select the S3 service, enter the bucket name, and click on the **Management** tab. Under the **Lifecycle** section, click **Add lifecycle rule** to create a new rule.
41
+
42
+
2. Input a rule name, select the object prefix, and configure the rule actions: **Permanently delete noncurrent versions of objects**.
43
+
44
+
3. Input the Days after object become noncurrent: 7 days recommended.
45
+
46
+
4. Input the Number of versions to retain: 0 recommended.
47
+
48
+
5. Click **Create rule** to save the lifecycle policy.
49
+
50
+
- Configure lifecycle rules to clean up expired delete markers and incomplete multipart uploads.
51
+
52
+
1. Go to the AWS Management Console, select the S3 service, enter the bucket name, and click on the **Management** tab. Under the **Lifecycle** section, click **Add lifecycle rule** to create a new rule.
45
53
46
-
2. Input a rule name, select the object prefix, and configure the rule actions: **Permanently delete noncurrent versions of objects**.
54
+
2. Input a rule name, select the object prefix, and configure the rule actions: **Delete expired object delete markers or incomplete multipart uploads**.
47
55
48
-
3.Input the Days after object become noncurrent: 7 days recommended.
56
+
3.Enable both options by toggling the checkboxes:
49
57
50
-
4. Input the Number of versions to retain: 0 recommended.
58
+
-**Expired object delete markers**: Removes delete markers for expired objects
59
+
-**Incomplete multipart uploads**: Cleans up incomplete multipart uploads after the specified number of days
51
60
52
-
5. Click **Create rule** to save the lifecycle policy.
61
+
4. Click **Create rule** to save the lifecycle policy.
0 commit comments