Standalone Explorers

Other Apps | Release Notes | Free Trial or Purchase

The S3 Explorer desktop application allows users to interact with object storage through a familiar file explorer like interface. From the menu, or using drag and drop, users can easily upload, download and delete files and folders. Copying, moving and renaming objects and folders is also supported. Objects can be quickly located through search, and sensitive data automatically encrypted on upload.

Explorers are available for private and public clouds supporting:

• S3 and S3-Compatible Object Storage
• Google Cloud Storage
• Microsoft Azure Blob Storage
• OpenStack Swift Storage
• Rackspace Cloud Files

After providing the storage endpoint and account credentials the explorer is ready to use.

The top-level folders represent object storage buckets (or containers) that can be easily created, renamed, and deleted through the explorer.

The explorer supports renaming a bucket by creating a new bucket, copying objects from the old one to the new one, and deleting the old files and then the old bucket. Object copies are executed server-side, on the object storage.

Buckets created through the explorer will be created in the default region. They can continue to be created through the storage console of course where other settings can be changed.

Files and folders can be copied, deleted, moved, and renamed.

The explorer supports folder operations by applying the operation to each object in that folder hierarchy. For example, for a folder “copy”, the explorer will ask, for each file, that object storage makes a copy to the new location.

Drag and drop files and folders between local and object storage. Use object storage for offsite backup, data migration or to free up space.

Use a secret client key to automatically encrypt on upload and download.

The explorer is optimized for large files and deep folder hierarchies. Uploads and downloads are streamed.

See also Object Storage Drive vs. Object Storage Explorer: The Case for Using Both

Quickly locate objects through an integrated search.

Fully customizable for white label, OEM or corporate use. Contact us for more information.

See also Object Storage Drive vs. Object Storage Explorer: The Case for Using Both

For purchase, pricing and trials see https://storagemadeeasy.com/standalonetools/

The installation process is simple and requires minimal configurations.

Latest system requirements at Standalone Explorer Release Notes.

Authentication is specific to the storage provider, typically an id and password. An endpoint can be provided for private clouds.

• Azure - Account name and either your primary or secondary key
• Google - Open the Cloud Storage Settings page in the Google Cloud Platform Console; Select “Interoperability”; If you have not set up interoperability before, click “Enable interoperability access”; Click “Create a new key”.
• IBM Cloud Object Storage - (IBM COS) Endpoint, Access key ID, and secret access key. The endpoint must not include the bucket name.
• OpenStack Swift - User name, password, and either Tenant Name or Tenant Id. Contact your provider for more information. For OpenStack Swift the option “Use internal URLs when possible” is an optimization available when the storage is deployed on a local network.
• Rackspace Files - User name and API key.
• S3 - AWS Access key (access key ID and secret access key). The endpoint must not include the bucket name. To create an access key for AWS see Understanding and getting your AWS credentials. For AWS the access key will look like “AKIAIOSFODNN7EXAMPLE” and the secret access key like ““wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKE”.

The Connections Setting dialog is available from the Authentication page and from the “Change Settings” icon on the explorer itself. Connections Settings allow the Internet Proxy settings for the Explorer to be managed independently of the Windows Operating System.