Although S3 can coexist in an SVM with other protocols, you might want to create a new SVM to isolate the namespace and workload.
The following command creates an SVM for data access in the IPspace ipspaceA:
cluster-1::> vserver create -vserver svm1.example.com -rootvolume root_svm1 -aggregate aggr1
-rootvolume-security-style unix -language C.UTF-8 -ipspace ipspaceA
[Job 2059] Job succeeded:
Vserver creation completed
The following command shows that an SVM was created with a root volume of 1 GB, and it was started automatically and is in running state. The root volume has a default export policy that does not include any rules, so the root volume is not exported upon creation. By default, the vsadmin user account is created and is in the locked state. The vsadmin role is assigned to the default vsadmin user account.
cluster-1::> vserver show -vserver svm1.example.com Vserver: svm1.example.com Vserver Type: data Vserver Subtype: default Vserver UUID: b8375669-19b0-11e5-b9d1-00a0983d9736 Root Volume: root_svm1 Aggregate: aggr1 NIS Domain: - Root Volume Security Style: unix LDAP Client: - Default Volume Language Code: C.UTF-8 Snapshot Policy: default Comment: Quota Policy: default List of Aggregates Assigned: - Limit on Maximum Number of Volumes allowed: unlimited Vserver Admin State: running Vserver Operational State: running Vserver Operational State Stopped Reason: - Allowed Protocols: nfs, cifs Disallowed Protocols: - QoS Policy Group: - Config Lock: false IPspace Name: ipspaceA