Let your AI team run Amazon S3 (Your Account) for you.

What your agent does with Amazon S3 (Your Account)

Connect Vezra to S3 buckets in your own AWS account (or any S3-compatible endpoint — R2, MinIO, Wasabi) using an IAM access key. Different from the managed object-storage connector — here every byte stays in the bucket-owner's account.

• Objects: list / get / put / delete / head / copy / restore (Glacier) + tagging + ACL get/put/delete
• Multipart uploads: create / list parts / upload part / complete / abort
• Presigned URLs for GET and PUT (short-lived)
• Buckets: list / head / get location / versioning / encryption / lifecycle / policy / CORS / website / public-access-block / replication / logging / tagging
• Object versioning: list-object-versions + get version
• Works with non-AWS S3-compatible providers via the optional Endpoint field (Cloudflare R2, MinIO, Wasabi, Backblaze B2)
• Default bucket field — actions can omit `bucket` and reuse the saved default
• Region pinning per-connection (cross-region calls still possible by passing explicit endpoint)
• SigV4 signing via the official AWS SDK — no custom signer to drift
• Server-side encryption negotiation (SSE-S3, SSE-KMS) by passing the right input fields
• Strict JSON sanitization — binary bodies are base64-encoded for transport safety
• Friendly auth errors ("invalid key", "missing s3:ListAllMyBuckets", etc.)