AWS Security ChangesHomeSearch

AWS amazonglacier documentation change

Service: amazonglacier · 2025-10-10 · Documentation low

File: amazonglacier/latest/dev/uploading-archive-mpu.md

Summary

Updated branding from 'Glacier' to 'Amazon Glacier' throughout, added deprecation notice for original standalone Amazon Glacier service (no new customers after 2025), and emphasized migration guidance to S3 Glacier storage classes.

Security assessment

Changes focus on service naming consistency, deprecation announcements, and migration recommendations. No security vulnerabilities, encryption changes, or access control updates are mentioned. The migration guidance relates to service evolution rather than addressing security weaknesses.

Diff

diff --git a/amazonglacier/latest/dev/uploading-archive-mpu.md b/amazonglacier/latest/dev/uploading-archive-mpu.md
index 454868305..15312fcd8 100644
--- a//amazonglacier/latest/dev/uploading-archive-mpu.md
+++ b//amazonglacier/latest/dev/uploading-archive-mpu.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 @@ Multipart Upload ProcessQuick Facts
-**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 @@ Multipart Upload ProcessQuick Facts
-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/).
@@ -32 +34 @@ If you're looking for archival storage solutions we suggest using the Glacier st
-As described in [Uploading an Archive in Amazon Glacier](./uploading-an-archive.html), we encourage Amazon Glacier (Glacier) customers to use Multipart Upload to upload archives greater than 100 mebibytes (MiB). 
+As described in [Uploading an Archive in Amazon Glacier](./uploading-an-archive.html), we encourage Amazon Glacier (Amazon Glacier) customers to use Multipart Upload to upload archives greater than 100 mebibytes (MiB). 
@@ -36 +38 @@ As described in [Uploading an Archive in Amazon Glacier](./uploading-an-archive.
-When you send a request to initiate a multipart upload, Glacier returns a multipart upload ID, which is a unique identifier for your multipart upload. Any subsequent multipart upload operations require this ID. This ID doesn't expire for at least 24 hours after Glacier completes the job. 
+When you send a request to initiate a multipart upload, Amazon Glacier returns a multipart upload ID, which is a unique identifier for your multipart upload. Any subsequent multipart upload operations require this ID. This ID doesn't expire for at least 24 hours after Amazon Glacier completes the job. 
@@ -48 +50 @@ In the initiate multipart upload request, you can also provide an optional archi
-For each part upload request, you must include the multipart upload ID you obtained in step 1. In the request, you must also specify the content range, in bytes, identifying the position of the part in the final archive. Glacier later uses the content range information to assemble the archive in proper sequence. Because you provide the content range for each part that you upload, it determines the part's position in the final assembly of the archive, and therefore you can upload parts in any order. You can also upload parts in parallel. If you upload a new part using the same content range as a previously uploaded part, the previously uploaded part is overwritten. 
+For each part upload request, you must include the multipart upload ID you obtained in step 1. In the request, you must also specify the content range, in bytes, identifying the position of the part in the final archive. Amazon Glacier later uses the content range information to assemble the archive in proper sequence. Because you provide the content range for each part that you upload, it determines the part's position in the final assembly of the archive, and therefore you can upload parts in any order. You can also upload parts in parallel. If you upload a new part using the same content range as a previously uploaded part, the previously uploaded part is overwritten. 
@@ -52 +54 @@ For each part upload request, you must include the multipart upload ID you obtai
-After uploading all the archive parts, you use the complete operation. Again, you must specify the upload ID in your request. Glacier creates an archive by concatenating parts in ascending order based on the content range you provided. Glacier response to a Complete Multipart Upload request includes an archive ID for the newly created archive. If you provided an optional archive description in the Initiate Multipart Upload request, Glacier associates it with the assembled archive. After you successfully complete a multipart upload, you cannot refer to the multipart upload ID. That means you cannot access parts associated with the multipart upload ID.
+After uploading all the archive parts, you use the complete operation. Again, you must specify the upload ID in your request. Amazon Glacier creates an archive by concatenating parts in ascending order based on the content range you provided. Amazon Glacier response to a Complete Multipart Upload request includes an archive ID for the newly created archive. If you provided an optional archive description in the Initiate Multipart Upload request, Amazon Glacier associates it with the assembled archive. After you successfully complete a multipart upload, you cannot refer to the multipart upload ID. That means you cannot access parts associated with the multipart upload ID.
@@ -61 +63 @@ If you stop a multipart upload, you cannot upload any more parts using that mult
-Amazon Glacier (Glacier) provides the following additional multipart upload API calls.
+Amazon Glacier (Amazon Glacier) provides the following additional multipart upload API calls.
@@ -63 +65 @@ Amazon Glacier (Glacier) provides the following additional multipart upload API
-  * List Parts—Using this operation, you can list the parts of a specific multipart upload. It returns information about the parts that you have uploaded for a multipart upload. For each list parts request, Glacier returns information for up to 1,000 parts. If there are more parts to list for the multipart upload, the result is paginated and a marker is returned in the response at which to continue the list. You need to send additional requests to retrieve subsequent parts. Note that the returned list of parts doesn't include parts that haven't completed uploading.
+  * List Parts—Using this operation, you can list the parts of a specific multipart upload. It returns information about the parts that you have uploaded for a multipart upload. For each list parts request, Amazon Glacier returns information for up to 1,000 parts. If there are more parts to list for the multipart upload, the result is paginated and a marker is returned in the response at which to continue the list. You need to send additional requests to retrieve subsequent parts. Note that the returned list of parts doesn't include parts that haven't completed uploading.
@@ -65 +67 @@ Amazon Glacier (Glacier) provides the following additional multipart upload API
-  * List Multipart Uploads—Using this operation, you can obtain a list of multipart uploads in progress. An in-progress multipart upload is an upload that you have initiated, but have not yet completed or stopped. For each list multipart uploads request, Glacier returns up to 1,000 multipart uploads. If there are more multipart uploads to list, then the result is paginated and a marker is returned in the response at which to continue the list. You need to send additional requests to retrieve the remaining multipart uploads.
+  * List Multipart Uploads—Using this operation, you can obtain a list of multipart uploads in progress. An in-progress multipart upload is an upload that you have initiated, but have not yet completed or stopped. For each list multipart uploads request, Amazon Glacier returns up to 1,000 multipart uploads. If there are more multipart uploads to list, then the result is paginated and a marker is returned in the response at which to continue the list. You need to send additional requests to retrieve the remaining multipart uploads.