Create a CloudFS filesystem
Creates a CloudFS filesystem. Provisioning is synchronous — typically a few seconds, up to a few minutes — and the filesystem is returned with status ready, together with its S3 bucket and metadata connection details. This response is the only time the filesystem’s meta_token — and the credential-bearing meta_url — are returned; store them securely. If the token is lost, issue a new one with the rotate-meta-token action. Names are unique within your organization: creating with an existing name returns a 422. Requests are idempotent: retrying with the same Idempotency-Key within 24 hours replays the original response instead of creating another filesystem.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
Unique key that makes the request idempotent (1-255 characters: letters, numbers, _, and -). Retrying with the same key within 24 hours replays the original response (marked with an Idempotent-Replayed: true header) instead of repeating the action. Reusing a key with a different request returns a 422; sending a key while the original request is still being processed returns a 409.
1 - 255^[A-Za-z0-9_-]+$Body
CloudFS filesystem creation request
Filesystem name, unique within your organization. Names are trimmed and lowercased; after normalization they may contain lowercase letters, numbers, ., _, and - only.
1 - 63^[a-z0-9._-]+$"agent-fs"
Region where the filesystem's storage and metadata are provisioned.
us-central-1, us-east-1, us-west-1 "us-east-1"
Response
CloudFS filesystem created successfully. This is the only response (besides rotate-meta-token) that includes meta_token.
A CloudFS filesystem, including its metadata credential. This shape is returned only by create and rotate-meta-token.