AWS amazonglacier documentation change
Summary
Updated service name references from 'S3 Glacier' to 'Glacier' and adjusted related links/terminology to align with branding changes. No functional changes to API headers or security requirements.
Security assessment
The changes are purely branding/naming updates (e.g., 'S3 Glacier' → 'Glacier') and link text adjustments. No modifications to security protocols, vulnerabilities, or encryption features were made. The security-related content about Signature Version 4 and date handling remains unchanged except for service name references.
Diff
diff --git a/amazonglacier/latest/dev/api-common-request-headers.md b/amazonglacier/latest/dev/api-common-request-headers.md index 8f0cffec7..3760d1522 100644 --- a//amazonglacier/latest/dev/api-common-request-headers.md +++ b//amazonglacier/latest/dev/api-common-request-headers.md @@ -5 +5 @@ -**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.** @@ -7 +7 @@ -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. @@ -11 +11 @@ If you're looking for archival storage solutions we suggest using the S3 Glacier -Amazon S3 Glacier (S3 Glacier) REST requests include headers that contain basic information about the request. The following table describes headers that can be used by all S3 Glacier REST requests. +Amazon Glacier (Glacier) REST requests include headers that contain basic information about the request. The following table describes headers that can be used by all Glacier REST requests. @@ -15 +15 @@ Header Name | Description | Required -`Authorization` | The header that is required to sign requests. S3 Glacier requires Signature Version 4. For more information, see [Signing Requests](./amazon-glacier-signing-requests.html). Type: String | Yes +`Authorization` | The header that is required to sign requests. Glacier requires Signature Version 4. For more information, see [Signing Requests](./amazon-glacier-signing-requests.html). Type: String | Yes @@ -17 +17 @@ Header Name | Description | Required -`Date` | The date that can be used to create the signature contained in the `Authorization` header. If the `Date` header is to be used for signing it must be specified in the ISO 8601 basic format. In this case, the `x-amz-date` header is not needed. Note that when `x-amz-date` is present, it always overrides the value of the `Date` header. If the Date header is not used for signing, it can be one of the full date formats specified by [RFC 2616](http://tools.ietf.org/html/rfc2616#section-3.3), section 3.3. For example, the following date/time `Wed, 10 Feb 2017 12:00:00 GMT` is a valid date/time header for use with S3 Glacier. If you are using the `Date` header for signing, then it must be in the ISO 8601 basic `YYYYMMDD'T'HHMMSS'Z'` format. Type: String Condition: If `Date` is specified but is not in ISO 8601 basic format, then you must also include the `x-amz-date` header. If `Date` is specified in ISO 8601 basic format, then this is sufficient for signing requests and you do not need the `x-amz-date` header. For more information, see [Handling Dates in Signature Version 4](https://docs.aws.amazon.com/general/latest/gr/sigv4-date-handling.html) in the _Amazon Web Services Glossary_. | Conditional +`Date` | The date that can be used to create the signature contained in the `Authorization` header. If the `Date` header is to be used for signing it must be specified in the ISO 8601 basic format. In this case, the `x-amz-date` header is not needed. Note that when `x-amz-date` is present, it always overrides the value of the `Date` header. If the Date header is not used for signing, it can be one of the full date formats specified by [RFC 2616](http://tools.ietf.org/html/rfc2616#section-3.3), section 3.3. For example, the following date/time `Wed, 10 Feb 2017 12:00:00 GMT` is a valid date/time header for use with Glacier. If you are using the `Date` header for signing, then it must be in the ISO 8601 basic `YYYYMMDD'T'HHMMSS'Z'` format. Type: String Condition: If `Date` is specified but is not in ISO 8601 basic format, then you must also include the `x-amz-date` header. If `Date` is specified in ISO 8601 basic format, then this is sufficient for signing requests and you do not need the `x-amz-date` header. For more information, see [Handling Dates in Signature Version 4](https://docs.aws.amazon.com/general/latest/gr/sigv4-date-handling.html) in the _Amazon Web Services Glossary_. | Conditional @@ -20,2 +20,2 @@ Header Name | Description | Required -`x-amz-date` | The date used to create the signature in the Authorization header. The format must be ISO 8601 basic in the `YYYYMMDD'T'HHMMSS'Z'` format. For example, the following date/time `20170210T120000Z` is a valid `x-amz-date` for use with S3 Glacier. Type: String Condition: `x-amz-date` is optional for all requests; it can be used to override the date used for signing requests. If the `Date` header is specified in the ISO 8601 basic format, then `x-amz-date` is not needed. When `x-amz-date` is present, it always overrides the value of the `Date` header. For more information, see [Handling Dates in Signature Version 4](https://docs.aws.amazon.com/general/latest/gr/sigv4-date-handling.html) in the _Amazon Web Services Glossary_. | Conditional -`x-amz-glacier-version` | The S3 Glacier API version to use. The current version is `2012-06-01`. Type: String | Yes +`x-amz-date` | The date used to create the signature in the Authorization header. The format must be ISO 8601 basic in the `YYYYMMDD'T'HHMMSS'Z'` format. For example, the following date/time `20170210T120000Z` is a valid `x-amz-date` for use with Glacier. Type: String Condition: `x-amz-date` is optional for all requests; it can be used to override the date used for signing requests. If the `Date` header is specified in the ISO 8601 basic format, then `x-amz-date` is not needed. When `x-amz-date` is present, it always overrides the value of the `Date` header. For more information, see [Handling Dates in Signature Version 4](https://docs.aws.amazon.com/general/latest/gr/sigv4-date-handling.html) in the _Amazon Web Services Glossary_. | Conditional +`x-amz-glacier-version` | The Glacier API version to use. The current version is `2012-06-01`. Type: String | Yes