Skip to content

Commit 9af567c

Browse files
committed
docs(object): update checksums doc MTA-6196
1 parent 827a050 commit 9af567c

File tree

1 file changed

+24
-1
lines changed

1 file changed

+24
-1
lines changed

pages/object-storage/reference-content/supported-checksums.mdx

Lines changed: 24 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,8 @@ categories:
1515

1616
Checksums are critical components in ensuring data integrity within object storage systems. They are calculated values, typically a hash or a cyclic redundancy check (CRC), obtained from the content of an object. By comparing the stored checksum with one recalculated during data retrieval, storage systems can detect and often correct errors caused by corruption, transmission issues, or hardware failures.
1717

18+
## Supported checksum algorithms
19+
1820
Scaleway Object Storage supports several checksum algorithms that allow you to verify the integrity of your objects:
1921

2022
- **CRC32**: a non-cryptographic checksum that generates a 32-bit hash value used to detect errors in data transmission by applying a specific cyclic redundancy check (CRC) algorithm.
@@ -23,4 +25,25 @@ Scaleway Object Storage supports several checksum algorithms that allow you to v
2325

2426
- **SHA-1**: a cryptographic Secure Hash Algorithm (SHA) that generates a 160-bit (20-byte) hash value from input data.
2527

26-
- **SHA-256**: a cryptographic Secure Hash Algorithm that generates a 256-bit unique hash value, preferred for modern security protocols due to SHA-1 vulnerabilities.
28+
- **SHA-256**: a cryptographic Secure Hash Algorithm that generates a 256-bit unique hash value, preferred for modern security protocols due to SHA-1 vulnerabilities.
29+
30+
- **CRC-64/NVME (CRC64NVME)**: a 64-bit cyclic redundancy check algorithm specifically designed for data integrity verification in NVMe (Non-Volatile Memory Express) storage devices. This algorithm does not support composite checksums.
31+
32+
## Full object and composite checksum types
33+
34+
Scaleway Object Storage supports two types of checksums:
35+
36+
- **Full object checksums**: cryptographic hash values calculated over the entire content of an object to verify its integrity and detect any corruption or unauthorized changes.
37+
38+
- **Composite object checksums**: hash values calculated by combining the checksums of individual parts or segments of a multipart object, allowing verification of the integrity of the entire object assembled from its parts.
39+
40+
The table below shows the checksum types supported by each algorithm for multipart uploads:
41+
42+
| Checksum algorithm | Full object | Composite |
43+
|---|---|---|
44+
| **CRC-64/NVME (CRC64NVME)** | Yes | No |
45+
| **CRC-32 (CRC32)** | Yes | Yes |
46+
| **CRC-32C (CRC32C)** | Yes | Yes |
47+
| **SHA-1 (SHA1)** | No | Yes |
48+
| **SHA-256 (SHA256)** | No | Yes |
49+

0 commit comments

Comments
 (0)