AWS amazonglacier documentation change
Summary
Updated service name references from 'S3 Glacier' to 'Glacier' throughout the document, adjusted storage class terminology, and modified example payload text. No functional changes to authentication process.
Security assessment
Changes are purely terminological (rebranding 'S3 Glacier' to 'Glacier') and do not alter security mechanisms. The signature calculation process, encryption references, and authentication requirements remain unchanged. No evidence of addressing vulnerabilities or security incidents.
Diff
diff --git a/amazonglacier/latest/dev/amazon-glacier-signing-requests.md b/amazonglacier/latest/dev/amazon-glacier-signing-requests.md index eae7220d9..95034c52d 100644 --- a//amazonglacier/latest/dev/amazon-glacier-signing-requests.md +++ b//amazonglacier/latest/dev/amazon-glacier-signing-requests.md @@ -7 +7 @@ Example Signature CalculationCalculating Signatures for the Streaming Operations -**This page is only for existing customers of the S3 Glacier service using Vaults and the original REST API from 2012.** +**This page is only for existing customers of the Glacier service using Vaults and the original REST API from 2012.** @@ -9 +9 @@ Example Signature CalculationCalculating Signatures for the Streaming Operations -If you're looking for archival storage solutions we suggest using the S3 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 [S3 Glacier storage classes](https://aws.amazon.com/s3/storage-classes/glacier/) and [Long-term data storage using S3 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 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. @@ -13 +13 @@ If you're looking for archival storage solutions we suggest using the S3 Glacier -S3 Glacier requires that you authenticate every request you send by signing the request. To sign a request, you calculate a digital signature using a cryptographic hash function. A cryptographic hash is a function that returns a unique hash value based on the input. The input to the hash function includes the text of your request and your secret access key. The hash function returns a hash value that you include in the request as your signature. The signature is part of the `Authorization` header of your request. +Glacier requires that you authenticate every request you send by signing the request. To sign a request, you calculate a digital signature using a cryptographic hash function. A cryptographic hash is a function that returns a unique hash value based on the input. The input to the hash function includes the text of your request and your secret access key. The hash function returns a hash value that you include in the request as your signature. The signature is part of the `Authorization` header of your request. @@ -15 +15 @@ S3 Glacier requires that you authenticate every request you send by signing the -After receiving your request, S3 Glacier recalculates the signature using the same hash function and input that you used to sign the request. If the resulting signature matches the signature in the request, S3 Glacier processes the request. Otherwise, the request is rejected. +After receiving your request, Glacier recalculates the signature using the same hash function and input that you used to sign the request. If the resulting signature matches the signature in the request, Glacier processes the request. Otherwise, the request is rejected. @@ -17 +17 @@ After receiving your request, S3 Glacier recalculates the signature using the sa -S3 Glacier supports authentication using [AWS Signature Version 4](https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html). The process for calculating a signature can be broken into three tasks: +Glacier supports authentication using [AWS Signature Version 4](https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html). The process for calculating a signature can be broken into three tasks: @@ -21 +21 @@ S3 Glacier supports authentication using [AWS Signature Version 4](https://docs. -Rearrange your HTTP request into a canonical format. Using a canonical form is necessary because S3 Glacier uses the same canonical form when it recalculates a signature to compare with the one you sent. +Rearrange your HTTP request into a canonical format. Using a canonical form is necessary because Glacier uses the same canonical form when it recalculates a signature to compare with the one you sent. @@ -29 +29 @@ Create a string that you will use as one of the input values to your cryptograph -Create a signature for your request by using a cryptographic hash function that accepts two input strings: your _string to sign_ and a _derived key_. The _derived key_ is calculated by starting with your secret access key and using the _credential scope_ string to create a series of hash-based message authentication codes (HMACs). Note that the hash function used in this signing step is not the tree-hash algorithm used in S3 Glacier APIs that upload data. +Create a signature for your request by using a cryptographic hash function that accepts two input strings: your _string to sign_ and a _derived key_. The _derived key_ is calculated by starting with your secret access key and using the _credential scope_ string to create a series of hash-based message authentication codes (HMACs). Note that the hash function used in this signing step is not the tree-hash algorithm used in Glacier APIs that upload data. @@ -141 +141 @@ Similarly, in C# you can calculate the SHA256 hash of the payload data as shown -The following example walks you through the details of creating a signature for [Upload Archive (POST archive)](./api-archive-post.html), one of the two streaming APIs in S3 Glacier. The example assumes the following: +The following example walks you through the details of creating a signature for [Upload Archive (POST archive)](./api-archive-post.html), one of the two streaming APIs in Glacier. The example assumes the following: @@ -147 +147 @@ The following example walks you through the details of creating a signature for - * The content payload is a string "Welcome to S3 Glacier." + * The content payload is a string "Welcome to Glacier."