What this means in practice
Credentials are encrypted at rest and remain on the server; the agent can work with object names and prefixes, not inspect your secret keys.
Practical guidance
You can connect an R2 or S3 bucket for supported agent, workflow, and SDK actions. The credentials are encrypted at rest and remain on the server; they are not placed in prompts for the agent to read. The agent can work with bucket prefixes and objects through the supported actions, while the secret keys remain protected as connection credentials.
When connecting a bucket, use credentials scoped to the access the integration needs and verify the bucket and prefix before running a task. Start with a read operation to confirm that the expected objects are visible. Then review any write request before allowing it, especially if it targets an existing prefix. This setup lets you use your own storage while keeping credentials out of conversation text and preserving a clear boundary around which objects are in scope.