Search (SHIFT+S)
ECS Management API
ECS Object Service API
-
Amazon S3
- S3 Bucket
- S3 Bucket ACL
- S3 Bucket Cors
- S3 Bucket Empty Status Operations
- S3 Bucket Is Stale Allowed
- S3 Bucket Lifecycle
- S3 Bucket List Fanout (Cloud DVR)
- S3 Bucket List Uploads
- S3 Bucket Location
- S3 Bucket Lock Configuration Operations
- S3 Bucket Object Lock Operations
- S3 Bucket Policy
- S3 Bucket Versioning
- S3 Bucket Versions
- S3 Data Node
- S3 Metadata Key List
- S3 Metadata Key System List
- S3 Metadata Search
- S3 Multi Object Delete
- S3 Object
- S3 Object ACL
- S3 Object Detailed Replication Status Operations
- S3 Object Init Uploads
- S3 Object Legal Hold Operations
- S3 Object Replication Info Operations
- S3 Object Retention Operations
- S3 Object Tagging Operations
- S3 Object Uploads
- S3 Options
- S3 Ping
- S3 Retention Update Operation
- S3 Select Operations
- EMC Atmos
- OpenStack Swift
ECS API Changes
Create Subtenant
PUT /
Create new subtenant. Only authenticated users can create subtenants. Anonymous requests are never allowed to create subtenants. The current user will be the subtenant owner.
Request Headers
| x-emc-date | optional | The current date and time according to the requester. Date is in UTC format. for example: Thu, 31 Jan 2008 19:37:28 GMT. Many HTTP clients set this header automatically. This date is used to check whether a request is valid within the web server's validity time window. For this purpose, the timestamp in the x-emc-date header takes priority over this header. The Web server first checks for the x-emc-date header and uses its timestamp. If the x-emc-date header is not present, the Web server checks for the Date header and uses its timestamp. |
| x-emc-uid | required | User id of an application that uses this API |
| x-emc-namespace | required | Namespace to be used for this subtenant. If the name space is not specified using the x-emc-namespace header and if the request is from a registered ViPR user, then we use the namespace associated with that user. If all of these attempts fail, then the request is rejected. |
| x-emc-vpool | required | The vPool to associate the new subtenant with. This determines the data stores which would be used to store the objects associated with this subtenant. If this header is not present, then we use the default vPool defined for the associated tenant. |
| x-emc-retention-period | optional | Implicitly applying retention period in seconds for all objects in subtenant, -1 denotes infinity |
| x-emc-retention-start-delay | optional | Specifies the time period in seconds after which retention will be effective |
Prerequisites
The following conditions must be met in order to call this operation.
Only authenticated users can create subtenants
Both host style and path style are specified with POST
Request Payload
No Request Payload
Response Headers
| x-emc-subtenantId | always | Subtenant id generated for this subtenant by the system. |