AWS amazonglacier documentation change
Summary
Updated branding from 'S3 Glacier' to 'Glacier' throughout the document, adjusted terminology for storage class references, and fixed internal links to reflect the rebranding.
Security assessment
The changes are purely branding and terminology updates (e.g., 'S3 Glacier' to 'Glacier'). No security vulnerabilities, encryption changes, or access control modifications were mentioned. Existing security features like 'advanced optional encryption features' remain referenced but were not added or modified.
Diff
diff --git a/amazonglacier/latest/dev/vault-inventory.md b/amazonglacier/latest/dev/vault-inventory.md index 5c1a493f5..56918bc20 100644 --- a//amazonglacier/latest/dev/vault-inventory.md +++ b//amazonglacier/latest/dev/vault-inventory.md @@ -7 +7 @@ About the Inventory -**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 @@ About the Inventory -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 -# Downloading a Vault Inventory in Amazon S3 Glacier +# Downloading a Vault Inventory in Amazon Glacier @@ -13 +13 @@ If you're looking for archival storage solutions we suggest using the S3 Glacier -After you upload your first archive to your vault, Amazon S3 Glacier (S3 Glacier) automatically creates a vault inventory and then updates it approximately once a day. After S3 Glacier creates the first inventory, it typically takes half a day and up to a day before that inventory is available for retrieval. You can retrieve a vault inventory from S3 Glacier with the following two-step process: +After you upload your first archive to your vault, Amazon Glacier (Glacier) automatically creates a vault inventory and then updates it approximately once a day. After Glacier creates the first inventory, it typically takes half a day and up to a day before that inventory is available for retrieval. You can retrieve a vault inventory from Glacier with the following two-step process: @@ -19 +19 @@ After you upload your first archive to your vault, Amazon S3 Glacier (S3 Glacier -A data retrieval policy can cause your initiate retrieval job request to fail with a `PolicyEnforcedException` exception. For more information about data retrieval policies, see [S3 Glacier Data Retrieval Policies](./data-retrieval-policy.html). For more information about the `PolicyEnforcedException` exception, see [Error Responses](./api-error-responses.html). +A data retrieval policy can cause your initiate retrieval job request to fail with a `PolicyEnforcedException` exception. For more information about data retrieval policies, see [Glacier Data Retrieval Policies](./data-retrieval-policy.html). For more information about the `PolicyEnforcedException` exception, see [Error Responses](./api-error-responses.html). @@ -26 +26 @@ A data retrieval policy can cause your initiate retrieval job request to fail wi -For example, retrieving an archive or a vault inventory requires you to first initiate a retrieval job. The job request is run asynchronously. When you initiate a retrieval job, S3 Glacier creates a job and returns a job ID in the response. When S3 Glacier completes the job, you can get the job output, the archive bytes, or the vault inventory data. +For example, retrieving an archive or a vault inventory requires you to first initiate a retrieval job. The job request is run asynchronously. When you initiate a retrieval job, Glacier creates a job and returns a job ID in the response. When Glacier completes the job, you can get the job output, the archive bytes, or the vault inventory data. @@ -30 +30 @@ The job must complete before you can get its output. To determine the status of - * Wait for job completion notification—You can specify an Amazon Simple Notification Service (Amazon SNS) topic to which S3 Glacier can post a notification after the job is completed. You can specify Amazon SNS topic using the following methods: + * Wait for job completion notification—You can specify an Amazon Simple Notification Service (Amazon SNS) topic to which Glacier can post a notification after the job is completed. You can specify Amazon SNS topic using the following methods: @@ -38 +38 @@ When you initiate a job, you can optionally specify an Amazon SNS topic. -You can set notification configuration for specific events on the vault (see [Configuring Vault Notifications in Amazon S3 Glacier](./configuring-notifications.html)). S3 Glacier sends a message to the specified SNS topic any time the specific event occur. +You can set notification configuration for specific events on the vault (see [Configuring Vault Notifications in Amazon Glacier](./configuring-notifications.html)). Glacier sends a message to the specified SNS topic any time the specific event occur. @@ -40 +40 @@ You can set notification configuration for specific events on the vault (see [Co -If you have notification configuration set on the vault and you also specify an Amazon SNS topic when you initiate a job, S3 Glacier sends job completion message to both the topics. +If you have notification configuration set on the vault and you also specify an Amazon SNS topic when you initiate a job, Glacier sends job completion message to both the topics. @@ -44 +44 @@ You can configure the SNS topic to notify you via email or store the message in - * Request job information explicitly—S3 Glacier also provides a describe job operation ([Describe Job (GET JobID)](./api-describe-job-get.html)) that enables you to poll for job information. You can periodically send this request to obtain job information. However, using Amazon SNS notifications is the recommended option. + * Request job information explicitly—Glacier also provides a describe job operation ([Describe Job (GET JobID)](./api-describe-job-get.html)) that enables you to poll for job information. You can periodically send this request to obtain job information. However, using Amazon SNS notifications is the recommended option. @@ -57 +57 @@ The information you get via SNS notification is the same as what you get by call - * [Downloading a Vault Inventory in Amazon S3 Glacier Using the AWS SDK for Java](./retrieving-vault-inventory-java.html) + * [Downloading a Vault Inventory in Amazon Glacier Using the AWS SDK for Java](./retrieving-vault-inventory-java.html) @@ -59 +59 @@ The information you get via SNS notification is the same as what you get by call - * [Downloading a Vault Inventory in Amazon S3 Glacier Using the AWS SDK for .NET](./retrieving-vault-inventory-sdk-dotnet.html) + * [Downloading a Vault Inventory in Amazon Glacier Using the AWS SDK for .NET](./retrieving-vault-inventory-sdk-dotnet.html) @@ -63 +63 @@ The information you get via SNS notification is the same as what you get by call - * [Downloading a Vault Inventory in Amazon S3 Glacier Using the AWS Command Line Interface](./retrieving-vault-inventory-cli.html) + * [Downloading a Vault Inventory in Amazon Glacier Using the AWS Command Line Interface](./retrieving-vault-inventory-cli.html) @@ -70 +70 @@ The information you get via SNS notification is the same as what you get by call -S3 Glacier updates a vault inventory at least once per day, starting on the day you first upload an archive to the vault. If there have been no archive additions or deletions to the vault since the last inventory, the inventory date is not updated. When you initiate a job for a vault inventory, S3 Glacier returns the last inventory it generated, which is a point-in-time snapshot and not real-time data. Note that after S3 Glacier creates the first inventory for the vault, it typically takes half a day and up to a day before that inventory is available for retrieval. +Glacier updates a vault inventory at least once per day, starting on the day you first upload an archive to the vault. If there have been no archive additions or deletions to the vault since the last inventory, the inventory date is not updated. When you initiate a job for a vault inventory, Glacier returns the last inventory it generated, which is a point-in-time snapshot and not real-time data. Note that after Glacier creates the first inventory for the vault, it typically takes half a day and up to a day before that inventory is available for retrieval. @@ -72 +72 @@ S3 Glacier updates a vault inventory at least once per day, starting on the day -You might not find it useful to retrieve a vault inventory for each archive upload. However, suppose you maintain a database on the client-side associating metadata about the archives you upload to S3 Glacier. Then, you might find the vault inventory useful to reconcile information, as needed, in your database with the actual vault inventory. You can limit the number of inventory items retrieved by filtering on the archive creation date or by setting a quota. For more information about limiting inventory retrieval, see [Range Inventory Retrieval](./api-initiate-job-post.html#api-initiate-job-post-vault-inventory-list-filtering). +You might not find it useful to retrieve a vault inventory for each archive upload. However, suppose you maintain a database on the client-side associating metadata about the archives you upload to Glacier. Then, you might find the vault inventory useful to reconcile information, as needed, in your database with the actual vault inventory. You can limit the number of inventory items retrieved by filtering on the archive creation date or by setting a quota. For more information about limiting inventory retrieval, see [Range Inventory Retrieval](./api-initiate-job-post.html#api-initiate-job-post-vault-inventory-list-filtering).