When you view your S3 DuraCloud account using a GUI client or the AWS CLI for the first time in a new account, you will notice a number of pre-existing buckets that have been created.
aws-sam-*: this is a deployment artifact bucket only. It is inaccessible.duracloud-$ID-bucket-requested: this bucket is used to make requests to create new buckets.duracloud-$ID-logs: this bucket collects raw audit trail events from AWS. It is inaccessible.duracloud-$ID-managed: this bucket is used to deposit generated files such as audit history, exports, inventory, and reports. It is read-only.duracloud-$ID-private: a default private bucketduracloud-$ID-public: a default public bucket (files uploaded here will have a publicly accessible URL)
...
The duracloud-$ID-managed bucket will use these prefixes (folders) over time:
audit: audit logsbucket-requested: receives status reports on bucket creation request outcomesexports: CSV of checksum status checks and schedulesinventory: receives inventory CSV files per user bucket createdlogs:receives status reports such as bucket creation request outcomesreports: storage usage reports in HTML format
More information about the data available in the -managed bucket is available at Reports.
| Message Box | ||||||
|---|---|---|---|---|---|---|
| ||||||
If the AWS account is used for other purposes besides DuraCloud, it’s possible that other buckets may also exist. This will also be the case if there are multiple stacks per account. However, the access credentials given out for using DuraCloud will only work with the eligible stack resources associated with the user credentials. |
...