Select buckets for S3 auditing
-
PDF of this doc site
- Cluster administration
-
Volume administration
- Logical storage management with the CLI
-
NAS storage management
- Configure NFS with the CLI
- Manage NFS with the CLI
-
Manage SMB with the CLI
- Manage file access using SMB
- SAN storage management
- Security and data encryption
-
Data protection and disaster recovery
- Data protection with the CLI
Collection of separate PDF docs
Creating your file...
You must specify which buckets to audit in an audit-enabled SVM.
-
An SVM enabled for S3 auditing.
S3 auditing configurations are enabled on a per-SVM basis, but you must select the buckets in SVMS that are enabled for audit. If you add buckets to the SVM and you want the new buckets to be audited, you must select them with this procedure. You can also have non-audited buckets in an SVM enabled for S3 auditing.
Auditing configurations persist for buckets until removed by the vserver object-store-server audit object-select delete
command.
Select a bucket for S3 auditing:
vserver object-store-server audit event-selector create -vserver svm_name -bucket bucket_name [[-access] {read-only|write-only|all}] [[-permission] {allow-only|deny-only|all}]
-
-access
- specifies the type of event access to be audited:read-only
,write-only
orall
(default isall
). -
-permission
- specifies the type of event permission to be audited:allow-only
,deny-only
orall
(default isall
).
The following example creates a bucket auditing configuration that only logs allowed events with read-only access:
cluster1::> vserver object-store-server audit event-selector create -vserver vs1 -bucket test-bucket -access read-only -permission allow-only