AWS amazonglacier documentation change
Summary
Updated branding from 'Glacier' to 'Amazon Glacier', added deprecation notice for original Glacier service, and emphasized migration to S3 Glacier storage classes. Enhanced documentation about SHA256 hash verification process.
Security assessment
The changes primarily involve service naming consistency and deprecation announcements. While SHA256 hash verification is mentioned as a data integrity mechanism, this is existing security documentation rather than new security content. No vulnerabilities or security incidents are addressed.
Diff
diff --git a/amazonglacier/latest/dev/api-upload-part.md b/amazonglacier/latest/dev/api-upload-part.md index 814c9082d..7adc433d6 100644 --- a//amazonglacier/latest/dev/api-upload-part.md +++ b//amazonglacier/latest/dev/api-upload-part.md @@ -3 +3 @@ -[Documentation](/index.html)[Amazon S3 Glacier](/glacier/index.html)[Developer Guide](introduction.html) +[Documentation](/index.html)[Amazon Glacier](/glacier/index.html)[Developer Guide](introduction.html) @@ -7 +7 @@ DescriptionRequestsResponsesExampleRelated Sections -**This page is only for existing customers of the Glacier service using Vaults and the original REST API from 2012.** +**This page is only for existing customers of the Amazon Glacier service using Vaults and the original REST API from 2012.** @@ -9 +9,3 @@ DescriptionRequestsResponsesExampleRelated Sections -If you're looking for archival storage solutions we suggest using the Glacier storage classes in Amazon S3, **S3 Glacier Instant Retrieval** , **S3 Glacier Flexible Retrieval** , and **S3 Glacier Deep Archive**. To learn more about these storage options, see [Glacier storage classes](https://aws.amazon.com/s3/storage-classes/glacier/) and [Long-term data storage using Glacier storage classes](https://docs.aws.amazon.com/AmazonS3/latest/userguide/glacier-storage-classes) in the _Amazon S3 User Guide_. These storage classes use the Amazon S3 API, are available in all regions, and can be managed within the Amazon S3 console. They offer features like Storage Cost Analysis, Storage Lens, advanced optional encryption features, and more. +If you're looking for archival storage solutions, we recommend using the Amazon Glacier storage classes in Amazon S3, S3 Glacier Instant Retrieval, S3 Glacier Flexible Retrieval, and S3 Glacier Deep Archive. To learn more about these storage options, see [Amazon Glacier storage classes](https://aws.amazon.com/s3/storage-classes/glacier/). + +Amazon Glacier (original standalone vault-based service) will no longer accept new customers starting December 15, 2025, with no impact to existing customers. Amazon Glacier is a standalone service with its own APIs that stores data in vaults and is distinct from Amazon S3 and the Amazon S3 Glacier storage classes. Your existing data will remain secure and accessible in Amazon Glacier indefinitely. No migration is required. For low-cost, long-term archival storage, AWS recommends the [Amazon S3 Glacier storage classes](https://aws.amazon.com/s3/storage-classes/glacier/), which deliver a superior customer experience with S3 bucket-based APIs, full AWS Region availability, lower costs, and AWS service integration. If you want enhanced capabilities, consider migrating to Amazon S3 Glacier storage classes by using our [AWS Solutions Guidance for transferring data from Amazon Glacier vaults to Amazon S3 Glacier storage classes](https://aws.amazon.com/solutions/guidance/data-transfer-from-amazon-s3-glacier-vaults-to-amazon-s3/). @@ -19 +21 @@ For information about multipart upload, see [Uploading Large Archives in Parts ( -Amazon Glacier (Glacier) rejects your upload part request if any of the following conditions is true: +Amazon Glacier (Amazon Glacier) rejects your upload part request if any of the following conditions is true: @@ -21 +23 @@ Amazon Glacier (Glacier) rejects your upload part request if any of the followin - * SHA256 tree hash does not match—To ensure that part data is not corrupted in transmission, you compute a SHA256 tree hash of the part and include it in your request. Upon receiving the part data, Glacier also computes a SHA256 tree hash. If the two hash values don't match, the operation fails. For information about computing a SHA256 tree hash, see [Computing Checksums](./checksum-calculations.html). + * SHA256 tree hash does not match—To ensure that part data is not corrupted in transmission, you compute a SHA256 tree hash of the part and include it in your request. Upon receiving the part data, Amazon Glacier also computes a SHA256 tree hash. If the two hash values don't match, the operation fails. For information about computing a SHA256 tree hash, see [Computing Checksums](./checksum-calculations.html). @@ -40 +42 @@ This operation is idempotent. If you upload the same part multiple times, the da -You send this HTTP `PUT` request to the URI of the upload ID that was returned by your Initiate Multipart Upload request. Glacier uses the upload ID to associate part uploads with a specific multipart upload. The request must include a SHA256 tree hash of the part data (`x-amz-SHA256-tree-hash` header), a SHA256 linear hash of the entire payload (`x-amz-content-sha256` header), the byte range (`Content-Range` header), and the length of the part in bytes (`Content-Length` header). +You send this HTTP `PUT` request to the URI of the upload ID that was returned by your Initiate Multipart Upload request. Amazon Glacier uses the upload ID to associate part uploads with a specific multipart upload. The request must include a SHA256 tree hash of the part data (`x-amz-SHA256-tree-hash` header), a SHA256 linear hash of the entire payload (`x-amz-content-sha256` header), the byte range (`Content-Range` header), and the length of the part in bytes (`Content-Length` header). @@ -71 +73 @@ Name | Description | Required -`Content-Range` | Identifies the range of bytes in the assembled archive that will be uploaded in this part. Glacier uses this information to assemble the archive in the proper sequence. The format of this header follows [RFC 2616](http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.16). An example header is `Content-Range:bytes 0-4194303/*`. Type: String Default: None Constraints: The range cannot be greater than the part size that you specified when you initiated the multipart upload. | Yes +`Content-Range` | Identifies the range of bytes in the assembled archive that will be uploaded in this part. Amazon Glacier uses this information to assemble the archive in the proper sequence. The format of this header follows [RFC 2616](http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.16). An example header is `Content-Range:bytes 0-4194303/*`. Type: String Default: None Constraints: The range cannot be greater than the part size that you specified when you initiated the multipart upload. | Yes @@ -81 +83 @@ The request body contains the data to upload. -Upon a successful part upload, Glacier returns a `204 No Content` response. +Upon a successful part upload, Amazon Glacier returns a `204 No Content` response. @@ -97 +99 @@ Name | Description -`x-amz-sha256-tree-hash` | The SHA256 tree hash that Glacier computed for the uploaded part. Type: String +`x-amz-sha256-tree-hash` | The SHA256 tree hash that Amazon Glacier computed for the uploaded part. Type: String @@ -134 +136 @@ To upload the next part, the procedure is the same; however, you must calculate -The parts can be uploaded in any order; Glacier uses the range specification for each part to determine the order in which to assemble them. +The parts can be uploaded in any order; Amazon Glacier uses the range specification for each part to determine the order in which to assemble them.