AWS amazonglacier documentation change
Summary
Updated branding from 'Glacier' to 'Amazon Glacier', added deprecation notice for original standalone service (no new customers after 2025), and emphasized migration guidance to S3 Glacier storage classes
Security assessment
The changes focus on service naming consistency, deprecation announcements, and migration recommendations. No specific security vulnerabilities or mitigations are mentioned. Security-related content about request signing and checksums remains unchanged except for branding updates.
Diff
diff --git a/amazonglacier/latest/dev/amazon-glacier-api.md b/amazonglacier/latest/dev/amazon-glacier-api.md index 12ee258cb..52bf54604 100644 --- a//amazonglacier/latest/dev/amazon-glacier-api.md +++ b//amazonglacier/latest/dev/amazon-glacier-api.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) @@ -5 +5 @@ -**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.** @@ -7 +7,3 @@ -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/). @@ -13 +15 @@ Amazon Glacier supports a set of operations—specifically, a set of RESTful API -You can use any programming library that can send HTTP requests to send your REST requests to Glacier. When sending a REST request, Glacier requires that you authenticate every request by signing the request. Additionally, when uploading an archive, you must also compute the checksum of the payload and include it in your request. For more information, see [Signing Requests](./amazon-glacier-signing-requests.html). +You can use any programming library that can send HTTP requests to send your REST requests to Amazon Glacier. When sending a REST request, Amazon Glacier requires that you authenticate every request by signing the request. Additionally, when uploading an archive, you must also compute the checksum of the payload and include it in your request. For more information, see [Signing Requests](./amazon-glacier-signing-requests.html). @@ -15 +17 @@ You can use any programming library that can send HTTP requests to send your RES -If an error occurs, you need to know what Glacier sends in an error response so that you can process it. This section provides all this information, in addition to documenting the REST operations, so that you can make REST API calls directly. +If an error occurs, you need to know what Amazon Glacier sends in an error response so that you can process it. This section provides all this information, in addition to documenting the REST operations, so that you can make REST API calls directly. @@ -17 +19 @@ If an error occurs, you need to know what Glacier sends in an error response so -You can either use the REST API calls directly or use the Amazon SDKs that provide wrapper libraries. These libraries sign each request you send and compute the checksum of the payload in your request. Therefore, using the Amazon SDKs simplifies your coding task. This developer guide provides working examples of basic Glacier operations using the AWS SDK for Java and .NET. For more information see, [Using the AWS SDKs with Amazon Glacier](./using-aws-sdk.html). +You can either use the REST API calls directly or use the Amazon SDKs that provide wrapper libraries. These libraries sign each request you send and compute the checksum of the payload in your request. Therefore, using the Amazon SDKs simplifies your coding task. This developer guide provides working examples of basic Amazon Glacier operations using the AWS SDK for Java and .NET. For more information see, [Using the AWS SDKs with Amazon Glacier](./using-aws-sdk.html).