List Storage Configs
Parameters
Request
Response
Fields
Create Storage Config
Parameters (AWS S3)
Parameters (Cloudflare R2)
R2 reuses thes3_bucket_name and s3_bucket_prefix fields — it speaks the S3 API — but takes its own account and credentials. There is no region (R2 is a single global namespace), and s3_is_accelerated, s3_cloudfront_domain and s3_auth_method: iam_role are rejected: they are AWS features with no Cloudflare equivalent, and accepting them would store a configuration whose URLs point at a host that does not serve the bucket.
Parameters (Google Cloud Storage)
Request (AWS S3)
Response
Test Connection
is_verified and last_verified_at fields.
Parameters
Request
Response (Success)
Response (Failure)
Get Setup Info
google_federation— for new connections. Your role trusts Google (accounts.google.com) pinned to Avala’s Google service-account IDs (subjects) and to your organization’saudience.trust_policyis the complete trust policy, ready to paste. No Avala AWS account appears in it.availableistrueonce Avala reads new connections this way.avala_aws_account_idandexternal_id— for existing connections whose trust policy names an Avala AWS account withsts:AssumeRole. Unchanged, kept for compatibility.
Parameters
Request
Response
Delete Storage Config
Parameters
Request
Response
Returns204 No Content on success.
Supported Providers
Error Responses
Validation Error (400)
Unauthorized (401)
X-Avala-Api-Key header is missing or contains an invalid key.