AWS amazonglacier documentation change
Summary
Updated service name references from 'S3 Glacier' to 'Glacier' throughout the documentation, adjusted links to storage class documentation, and removed redundant 'S3' branding in terminology.
Security assessment
The changes are purely branding/naming convention updates (e.g., 'S3 Glacier' to 'Glacier') and do not introduce, modify, or address security-related content. No security vulnerabilities, policies, or features are discussed or altered in the diff.
Diff
diff --git a/amazonglacier/latest/dev/api-initiate-job-post.md b/amazonglacier/latest/dev/api-initiate-job-post.md index ccab157c1..d21a20883 100644 --- a//amazonglacier/latest/dev/api-initiate-job-post.md +++ b//amazonglacier/latest/dev/api-initiate-job-post.md @@ -7 +7 @@ Initializing an Archive or Vault Inventory Retrieval Job RequestsResponsesExampl -**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 @@ Initializing an Archive or Vault Inventory Retrieval Job RequestsResponsesExampl -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 -This operation initiates the following types of Amazon S3 Glacier (S3 Glacier) jobs: +This operation initiates the following types of Amazon Glacier (Glacier) jobs: @@ -45 +45 @@ Retrieving an archive or a vault inventory are asynchronous operations that requ -A data retrieval policy can cause your initiate retrieval job request to fail with a `PolicyEnforcedException`. 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`. 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). @@ -52 +52 @@ A data retrieval policy can cause your initiate retrieval job request to fail wi -The retrieval request is ran 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 (archive or inventory data). For information about getting job output, see the [Get Job Output (GET output)](./api-job-output-get.html) operation. +The retrieval request is ran 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 (archive or inventory data). For information about getting job output, see the [Get Job Output (GET output)](./api-job-output-get.html) operation. @@ -56 +56 @@ The job must complete before you can get its output. To determine when a job is - * Use an Amazon SNS notification— You can specify an Amazon SNS topic to which S3 Glacier can post a notification after the job is completed. You can specify an SNS topic per job request. The notification is sent only after S3 Glacier completes the job. In addition to specifying an SNS topic per job request, you can configure vault notifications for a vault so that job notifications are sent for all retrievals. For more information, see [Set Vault Notification Configuration (PUT notification-configuration)](./api-vault-notifications-put.html). + * Use an Amazon SNS notification— You can specify an Amazon SNS topic to which Glacier can post a notification after the job is completed. You can specify an SNS topic per job request. The notification is sent only after Glacier completes the job. In addition to specifying an SNS topic per job request, you can configure vault notifications for a vault so that job notifications are sent for all retrievals. For more information, see [Set Vault Notification Configuration (PUT notification-configuration)](./api-vault-notifications-put.html). @@ -67 +67 @@ The information you get via notification is same that you get by calling [Descri -If for a specific event, you add both the notification configuration on the vault and also specify an SNS topic in your initiate job request, S3 Glacier sends both notifications. For more information, see [Set Vault Notification Configuration (PUT notification-configuration)](./api-vault-notifications-put.html). +If for a specific event, you add both the notification configuration on the vault and also specify an SNS topic in your initiate job request, Glacier sends both notifications. For more information, see [Set Vault Notification Configuration (PUT notification-configuration)](./api-vault-notifications-put.html). @@ -71 +71 @@ If for a specific event, you add both the notification configuration on the vaul -S3 Glacier updates a vault inventory approximately once a 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. +Glacier updates a vault inventory approximately once a 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. @@ -73 +73 @@ S3 Glacier updates a vault inventory approximately once a day, starting on the d -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. +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. @@ -75 +75 @@ After S3 Glacier creates the first inventory for the vault, it typically takes h -You might not find it useful to retrieve a vault inventory for each archive upload. However, suppose that 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. For more information about the data fields returned in an inventory job output, see [Response Body](./api-job-output-get.html#api-job-output-get-responses-elements). +You might not find it useful to retrieve a vault inventory for each archive upload. However, suppose that 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. For more information about the data fields returned in an inventory job output, see [Response Body](./api-job-output-get.html#api-job-output-get-responses-elements). @@ -103 +103 @@ When initiating an archive retrieval job, you can specify one of the following o - * **`Bulk`** – Bulk is the lowest-cost tier for S3 Glacier, enabling you to retrieve large amounts, even petabytes, of data inexpensively in a day. Data accessed using the Bulk tier is typically made available within 5–12 hours. + * **`Bulk`** – Bulk is the lowest-cost tier for Glacier, enabling you to retrieve large amounts, even petabytes, of data inexpensively in a day. Data accessed using the Bulk tier is typically made available within 5–12 hours. @@ -108 +108 @@ When initiating an archive retrieval job, you can specify one of the following o -For more information about expedited and bulk retrievals, see [Retrieving S3 Glacier Archives](./downloading-an-archive-two-steps.html). +For more information about expedited and bulk retrievals, see [Retrieving Glacier Archives](./downloading-an-archive-two-steps.html). @@ -112 +112 @@ For more information about expedited and bulk retrievals, see [Retrieving S3 Gla -To initiate a job, you use the HTTP `POST` method and scope the request to the vault's `jobs` subresource. You specify details of the job request in the JSON document of your request. The job type is specified with the `Type` field. Optionally, you can specify an `SNSTopic` field to indicate an Amazon SNS topic to which S3 Glacier can post notification after it completes the job. +To initiate a job, you use the HTTP `POST` method and scope the request to the vault's `jobs` subresource. You specify details of the job request in the JSON document of your request. The job type is specified with the `Type` field. Optionally, you can specify an `SNSTopic` field to indicate an Amazon SNS topic to which Glacier can post notification after it completes the job. @@ -116 +116 @@ To initiate a job, you use the HTTP `POST` method and scope the request to the v -To post a notification to Amazon SNS, you must create the topic yourself if it doesn't already exist. S3 Glacier doesn't create the topic for you. The topic must have permissions to receive publications from a S3 Glacier vault. S3 Glacier doesn't verify if the vault has permission to publish to the topic. If the permissions are not configured appropriately, you might not receive notification even after the job completes. +To post a notification to Amazon SNS, you must create the topic yourself if it doesn't already exist. Glacier doesn't create the topic for you. The topic must have permissions to receive publications from a Glacier vault. Glacier doesn't verify if the vault has permission to publish to the topic. If the permissions are not configured appropriately, you might not receive notification even after the job completes. @@ -221 +221 @@ _Required_ : Yes -S3 Glacier creates the job. In the response, it returns the URI of the job. +Glacier creates the job. In the response, it returns the URI of the job. @@ -247 +247 @@ This operation does not return a response body. -This operation includes the following error or errors, in addition to the possible errors common to all Amazon S3 Glacier operations. For information about Amazon S3 Glacier errors and a list of error codes, see [Error Responses](./api-error-responses.html). +This operation includes the following error or errors, in addition to the possible errors common to all Amazon Glacier operations. For information about Amazon Glacier errors and a list of error codes, see [Error Responses](./api-error-responses.html). @@ -374 +374 @@ The following request is an example of a subsequent request to retrieve the next - * [Identity and Access Management for Amazon S3 Glacier](./security-iam.html) + * [Identity and Access Management for Amazon Glacier](./security-iam.html)