Configure recording storage
Use an organization credential withstorage:write:
us-east-1 when omitted.
Test connectivity
After creation, save the integration ID and test its credentials:data.connected: true. Test failures are reported as API errors; creating an integration alone does not guarantee remote storage access.
Manage the integration
You can list, inspect, update, and disable integrations. Normal responses includehas_secret but do not return the stored secret access key.
An update can change name, access_key_id, secret_access_key, or status (active or disabled). The endpoint, region, bucket, and path-style settings cannot be changed in place because existing recordings may refer to that storage destination.
Only one recording storage integration can be active per organization. If you need a different destination, disable the old integration and create a new one. Deleting an integration disables it; it does not delete the recordings stored in your external bucket.