s3.bucket-cors.set

Replace the bucket’s CORS rules

PUT /s3/api/buckets/{name}/corsIAM s3:PutBucketCORSChanges stateDestructive

The same rules `aws s3api put-bucket-cors` writes over the S3 API, for every bucket. The gateway answers browser preflights (OPTIONS) from them and adds Access-Control-* headers to matching responses, presigned URLs included. Example: --rules '{"allowedOrigins":["https://app.example.com"],"allowedMethods":["GET","PUT"],"allowedHeaders":["*"],"exposeHeaders":["ETag"],"maxAgeSeconds":3000}'

Request syntax

PUT /s3/api/buckets/{name}/cors
{
  "rules": "array of json"
}

Path parameters

  • nameRequired

    string

    Constraints: 3-63 chars, /^[a-z0-9][a-z0-9-]*[a-z0-9]$/

Request body

  • rulesRequired

    array of json

    The rules, replacing the current ones: { allowedOrigins, allowedMethods, allowedHeaders?, exposeHeaders?, maxAgeSeconds?, id? }; the first rule that matches a request applies

Response

200; data is { rules }: the CORS rules as saved.

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow s3:PutBucketCORS on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud s3 bucket-cors set name --rules '["example"]'

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_s3_bucket-cors_set.