Calling AIOZ Storage's S3 API Directly with Postman

There's no ready-made Postman collection to import here, despite what the name of AIOZ's own docs page suggests. What AIOZ Storage's Postman documentation actually walks through is building raw S3 requests by hand in Postman, authenticated with its built-in AWS Signature auth type and your access grant's key pair. This is the lowest-level way to talk to AIOZ Storage covered in this series, useful for debugging a request that's failing somewhere inside an SDK, or for testing a call before you write any code around it.

TL;DR:

• AIOZ's Postman docs describe manually configuring AWS Signature authentication per request, not importing a prebuilt collection.
• Auth setup is four fields: Access Key, Secret Key, Service Name (s3), and Region (us-east-1), the same access grant credentials the SDKs and CLI use.
• Every request targets s3.aiozstorage.network directly, with the bucket and object name in the URL path, not as request parameters.

Setting Up AWS Signature Auth in Postman

Every request in this guide uses Postman's built-in AWS Signature auth type rather than a manually-built Authorization header, sparing you from hand-implementing AWS's own Signature Version 4 signing process that both AWS and AIOZ Storage require underneath. In a new request, open the Authorization tab, select AWS Signature from the Type dropdown, and fill in:

Postman signs the request for you using these fields, the same request-signing process the AWS CLI and every SDK in this series handle internally. Region being us-east-1 regardless of where your data actually lives is the same placeholder pattern as the CLI and SDK guides, AIOZ Storage isn't region-partitioned, but the signing process requires a region value.

Bucket Operations

Create a bucket:

PUT / HTTP/1.1
Host: s3.aiozstorage.network/your-bucket-name

List your buckets:

GET / HTTP/1.1
Host: s3.aiozstorage.network

Delete a bucket:

DELETE /your-bucket-name HTTP/1.1
Host: s3.aiozstorage.network

In Postman, these become the request URL, https://s3.aiozstorage.network/your-bucket-name for create and delete, https://s3.aiozstorage.network for list, with the method set to match and AWS Signature auth applied.

Object Operations

List objects in a bucket:

GET /your-bucket-name HTTP/1.1

Upload an object:

PUT /your-bucket-name/your-object-name HTTP/1.1

Set the request body to the file or raw data you're uploading. Postman's Body tab supports raw text, JSON, or binary file uploads depending on what you're testing.

Retrieve an object:

GET /your-bucket-name/your-object-name HTTP/1.1

Delete an object:

DELETE /your-bucket-name/your-object-name HTTP/1.1

Copy an object:

PUT /dest-bucket-name/dest-object-name HTTP/1.1
x-amz-copy-source: /source-bucket-name/source-object-name

The copy source is set as a header, not a body or query parameter, x-amz-copy-source tells AIOZ Storage which existing object to copy into the destination path in the request line.

Deleting Multiple Objects in One Request

AIOZ's docs also list the standard S3 batch-delete operation, POST /?delete, which accepts an XML body listing multiple object keys to remove in a single call instead of one DELETE request per object. It's the same operation the AWS CLI's rm --recursive and most SDKs' batch-delete helpers call under the hood, useful in Postman mainly for confirming the exact request/response shape before wiring it into code.

Why Test with Postman Instead of an SDK?

Every SDK and the CLI in this series ultimately send the same signed HTTP requests shown above, they just build and sign them for you. Testing directly in Postman is useful when an SDK call is failing and it's not clear whether the problem is your code, your credentials, or the request itself, isolating the raw request removes a layer of abstraction. It's also a reasonable way to explore AIOZ Storage's S3 API for the first time without committing to a language or framework yet.

Frequently Asked Questions

Is there a downloadable Postman collection for AIOZ Storage?
No. AIOZ's own Postman documentation shows configuring individual requests by hand with AWS Signature auth, not importing a prebuilt collection file.

What credentials does Postman's AWS Signature auth need?
The same access key ID and secret access key from your AIOZ Storage access grant, the same pair used by the CLI and every SDK.

Why does AWS Signature auth in Postman ask for a Region if AIOZ Storage isn't region-partitioned?
The signing process requires a region value regardless of target. AIOZ's docs specify us-east-1 as the placeholder, the same value used across the CLI and SDK guides.

How do I upload a file's contents in a Postman PUT request?
Set the request body (Postman's Body tab) to the file or raw data, with the method set to PUT and the URL pointing at bucket-name/object-name.

How does copying an object work in raw S3 requests?
Send a PUT to the destination path with an x-amz-copy-source header pointing at the source bucket and object, not a request body.

Can I delete more than one object in a single request?
Yes, POST /?delete with an XML body listing multiple keys is the S3 batch-delete operation, the same one the AWS CLI and most SDKs use internally for recursive or bulk deletes.

Related Reading

• AIOZ Storage CLI Quickstart: AWS CLI with a Custom Endpoint - the same requests, sent through a purpose-built tool instead of built by hand.
• AIOZ Storage JavaScript SDK Quickstart - the same operations, signed and sent automatically by an SDK.
• AIOZ Storage Access Control: Macaroons and Access Grants - generating the Access Key and Secret Key this guide's auth setup needs.
• AIOZ Storage Glossary: Bucket, Passphrase, Macaroon - quick definitions for the access grant terms used throughout this guide.
• AIOZ Storage Developer Platform: SDKs, CLI, and Migrations - where direct API access fits alongside the SDKs, CLI, and migration guides on AIOZ Storage.

References

• AIOZ Storage Documentation: Postman
• Postman Documentation: AWS Signature Authorization
• AWS Documentation: Authenticating Requests (AWS Signature Version 4)