How to Integrate Object Storage with an S3 Client
Connect your Plenit Object Storage to an S3 client in two steps: gather the connection details in the dashboard and configure them in the client.
Object Storage is designed to store large volumes of application data (archiving, backup, IoT, DevOps) through an S3-compatible API.
That lets you connect it to any S3 client (CyberDuck, S3 Browser or another one) to manage your buckets from your computer. This guide gathers the data from the panel and configures it in the client.
👍 What you get
Your Object Storage bucket connected to an S3 client, ready to upload, download, and manage objects from the application.
Before you start
Access the administration panel at admin.plenit.com with permissions on the service.
Have an Object Storage. If you don't have one yet, set it up with the Quick Start for Object Storage.
Have an S3 client installed (for example, CyberDuck or S3 Browser) on your computer.
Step 1. Collect the connection data in the panel
At admin.plenit.com, go to Cloud Services → Object Storage and enter the subscription. An API integration needs four pieces of data:
Endpoint (access URL): click Connect in the subscription and choose access via client. The window shows the service URL.
Path (bucket name): appears as Bucket in that same window.
Access Key: in Users → Credentials.
Secret Key: in the same keys window.


🚧 Keep the Secret Key safe
The Secret Key is sensitive: treat it like a password and do not share it.
Together with the Access Key, it authenticates your S3 client's access to the bucket.
Step 2. Configure the S3 client
Enter that data in your S3 client. The exact way varies by application, but they all ask for the same thing: the URL from step 1, the keys (Access Key and Secret Key) and, depending on the user, the path. Common clients are CyberDuck and S3 Browser.


📘 Owner (OWNER) versus the rest of the users
There is a key difference depending on which user you connect with:
The owner (OWNER) of the bucket accesses the resource directly, without configuring anything else: the connection redirects them automatically.
The other users do not have direct access, so they must fill in the path with the name of the bucket they want to access.
If a user who is not the owner cannot see the content, it is almost always because they forgot to specify the path.
Conclusion
Integrating with an S3 client comes down to collecting four data items from the panel — endpoint, path, Access Key and Secret Key — and entering them in the application.
The only nuance worth remembering is the owner one: the OWNER enters directly, while the other users have to specify the bucket path.
With that, you manage your Object Storage from whichever S3 client you prefer, just like any storage compatible with the protocol.
Next steps
Review the service and bucket concepts in Object Storage concepts.
Review the organization of your buckets in Buckets and objects.
Understand how users and keys work in S3 access: users and credentials.
Last updated
Was this helpful?

