AWS Storage Gateway User Guide
Getting Notified About File Operations
"notification-id": "11b3106b-a18a-4890-9d47-a1a755ef5e47",
"request-received" : "2018-02-06T21:34:42Z",
"completed" : "2018-02-06T21:34:53Z"}
}
Field names Description
version The current version of the IAM policy.
id The ID that identifies the IAM policy.
detail-type A description of the of the event that triggered
the notification that was sent.
source The AWS service that is the source of the request
and notification.
account The id of the AWS account where the request and
notification were generated from.
time When the request to upload files to Amazon S3
was made.
region The AWS Region where the request and
notification was sent from.
resources The storage gateway resources that the policy
applies to.
source The AWS service that is the source of the request
and the notification.
event-type The CloudWatch Events that triggered the
notification.
notification-id The randomly generated ID of the notification
that was sent. This ID is in UUID format. This
is the notification ID that is returned when
NotfyWhenUploaded is called.
request-received When the gateway received the
NotfyWhenUploaded request.
completed When all the files in the working-set were
uploaded to Amazon S3.
Getting Refresh Cache Notification
For refresh cache notification use case, you could have two file gateways that map to the same Amazon
S3 bucket and the NFS client for Gateway1 uploads new files to the S3 bucket. The files will upload to S3
but they will not appear in Gateway2 until you refresh the cache. This is because Gateway2 uses a locally
cached version of the files in S3. You might want to do something with the files in Gateway2 when the
refresh cache is done. Large files could take a while to show up in gateway2 so you might want to be
notified when the cache refresh is done. You can request refresh cache notification from Gateway2 to
notify you when all the files are visible in Gateway2.
API Version 2013-06-30
201
To Next Page
Loading...