This page is only for existing customers of the S3 Glacier service using Vaults and the original REST API from 2012.
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
Set Vault Notification Configuration (PUT notification-configuration)
Description
Retrieving an archive and a vault inventory are asynchronous operations in Amazon S3 Glacier (S3 Glacier) for which you must first initiate a job and wait for the job to complete before you can download the job output. You can configure a vault to post a message to an Amazon Simple Notification Service (Amazon SNS) topic when these jobs complete. You can use this operation to set notification configuration on the vault. For more information, see Configuring Vault Notifications in Amazon S3 Glacier.
To configure vault notifications, send a PUT request to the
notification-configuration
subresource of the vault. A notification
configuration is specific to a vault; therefore, it is also referred to as a vault
subresource. The request should include a JSON document that provides an Amazon Simple Notification Service (Amazon SNS) topic and the events for which you want S3 Glacier to
send notifications to the topic.
You can configure a vault to publish a notification for the following vault events:
-
ArchiveRetrievalCompleted
— This event occurs when a job that was initiated for an archive retrieval is completed (Initiate Job (POST jobs)). The status of the completed job can beSucceeded
orFailed
. The notification sent to the SNS topic is the same output as returned from Describe Job (GET JobID). -
InventoryRetrievalCompleted
— This event occurs when a job that was initiated for an inventory retrieval is completed (Initiate Job (POST jobs)). The status of the completed job can beSucceeded
orFailed
. The notification sent to the SNS topic is the same output as returned from Describe Job (GET JobID).
Amazon SNS topics must grant permission to the vault to be allowed to publish notifications to the topic.
Requests
To set notification configuration on your vault, send a PUT request to the URI of the
vault's notification-configuration
subresource. You specify the
configuration in the request body. The configuration includes the Amazon SNS topic name
and an array of events that trigger notification to each topic.
Syntax
PUT /
AccountId
/vaults/VaultName
/notification-configuration HTTP/1.1 Host: glacier.Region
.amazonaws.com Date:Date
Authorization:SignatureValue
x-amz-glacier-version: 2012-06-01 { "SNSTopic":String
, "Events":[String
, ...] }
Note
The AccountId
value is the AWS account ID of the account that owns the vault. You can either specify an AWS account ID or optionally a single '-
' (hyphen), in which case Amazon S3 Glacier uses the AWS account ID associated with the credentials used to sign the request. If you use an account ID, do not include any hyphens ('-') in the ID.
Request Parameters
This operation does not use request parameters.
Request Headers
This operation uses only request headers that are common to all operations. For information about common request headers, see Common Request Headers.
Request Body
The JSON in the request body contains the following fields.
- Events
-
An array of one or more events for which you want S3 Glacier to send notification.
Valid Values:
ArchiveRetrievalCompleted
|InventoryRetrievalCompleted
Required: yes
Type: Array
- SNSTopic
-
The Amazon SNS topic ARN. For more information, go to Getting Started with Amazon SNS in the Amazon Simple Notification Service Getting Started Guide.
Required: yes
Type: String
Responses
In response, Amazon S3 Glacier (S3 Glacier) returns 204 No Content
if the notification configuration
is accepted.
Syntax
HTTP/1.1 204 No Content x-amzn-RequestId: x-amzn-RequestId Date: Date
Response Headers
This operation uses only request headers that are common to all operations. For information about common request headers, see Common Request Headers.
Response Body
This operation does not return a response body.
Errors
For information about Amazon S3 Glacier exceptions and error messages, see Error Responses.
Examples
The following example demonstrates how to configure vault notification.
Example Request
The following request sets the examplevault
notification configuration so that
notifications for two events (ArchiveRetrievalCompleted
and
InventoryRetrievalCompleted
) are sent to the Amazon SNS topic
arn:aws:sns:us-west-2:012345678901:mytopic
.
PUT /-/vaults/examplevault/notification-policy HTTP/1.1 Host: glacier.us-west-2.amazonaws.com x-amz-Date: 20170210T120000Z x-amz-glacier-version: 2012-06-01 Authorization: AWS4-HMAC-SHA256 Credential=AKIAIOSFODNN7EXAMPLE/20141123/us-west-2/glacier/aws4_request,SignedHeaders=host;x-amz-date;x-amz-glacier-version,Signature=9257c16da6b25a715ce900a5b45b03da0447acf430195dcb540091b12966f2a2 { "Events": ["ArchiveRetrievalCompleted", "InventoryRetrievalCompleted"], "SNSTopic": "arn:aws:sns:us-west-2:012345678901:mytopic" }
Example Response
A successful response returns a 204 No Content
.
HTTP/1.1 204 No Content x-amzn-RequestId: AAABZpJrTyioDC_HsOmHae8EZp_uBSJr6cnGOLKp_XJCl-Q Date: Wed, 10 Feb 2017 12:00:00 GMT
Related Sections
See Also
For more information about using this API in one of the language-specific Amazon SDKs, see the following: