AWS amazonglacier documentation change
Summary
Updated service name references from 'S3 Glacier' to 'Glacier' throughout documentation, removed redundant 'S3' prefixes in storage class references, and updated links to match new terminology
Security assessment
Changes are purely terminological updates to branding/naming conventions (S3 Glacier → Glacier). No security vulnerabilities, encryption practices, or access control mechanisms were modified. The operation description remains functionally identical.
Diff
diff --git a/amazonglacier/latest/dev/api-DeleteVaultAccessPolicy.md b/amazonglacier/latest/dev/api-DeleteVaultAccessPolicy.md index 635b2168c..657e348f4 100644 --- a//amazonglacier/latest/dev/api-DeleteVaultAccessPolicy.md +++ b//amazonglacier/latest/dev/api-DeleteVaultAccessPolicy.md @@ -7 +7 @@ DescriptionRequestsResponsesExamplesRelated SectionsSee Also -**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 @@ DescriptionRequestsResponsesExamplesRelated SectionsSee Also -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. @@ -15 +15 @@ If you're looking for archival storage solutions we suggest using the S3 Glacier -This operation deletes the access policy associated with the specified vault. The operation is eventually consistent—that is, it might take some time for Amazon S3 Glacier (S3 Glacier) to completely remove the access policy, and you might still see the effect of the policy for a short time after you send the delete request. +This operation deletes the access policy associated with the specified vault. The operation is eventually consistent—that is, it might take some time for Amazon Glacier (Glacier) to completely remove the access policy, and you might still see the effect of the policy for a short time after you send the delete request. @@ -50 +50 @@ This operation does not have a request body. -In response, S3 Glacier returns `204 No Content` if the policy is successfully deleted. +In response, Glacier returns `204 No Content` if the policy is successfully deleted. @@ -69 +69 @@ This operation does not return a response body. -For information about Amazon S3 Glacier exceptions and error messages, see [Error Responses](./api-error-responses.html). +For information about Amazon Glacier exceptions and error messages, see [Error Responses](./api-error-responses.html). @@ -89 +89 @@ In this example, a `DELETE` request is sent to the `access-policy` subresource o -In response, if the policy is successfully deleted S3 Glacier returns a `204 No Content` as shown in the following example. +In response, if the policy is successfully deleted Glacier returns a `204 No Content` as shown in the following example.