Amazon S3 file management

Take the helm of your cloud storage.

Find, organize, automate and cost-control your Amazon S3 files from one place — without the AWS console, scripts or command-line tools.

files in one bucket, benchmarked
200,000
until a download link expires
15 min
AWS keys stored with an IAM role
0

The Files window is live: type inv in “Filename contains”.

Illustration of the StorHelm Files screen with sample data. The filename search works.

104,882 file(s)

Sample files in the folder inbound/edi/2026-11
Name Size
INV_810_20261113_0412.xml 18.2 KB
ORD_850_20261113_0398.xml 21.4 KB
INV_810_20261112_2231.xml 9.1 KB
ASN_856_20261112_1907.xml 34.0 KB
export_customers_2026-11-10.csv 4.2 MB
report_q3_2026.pdf 2.1 MB
backup_2026-10-31.tar.gz 1.8 GB

01 — What it solves

Six things S3 makes hard, handled.

StorHelm is for teams that receive, process and archive large volumes of files, and for staff who need those files without AWS console access.

  1. Problem: S3 cannot search by filename or filter by date

    StorHelm's answer: Instant search and date filters over an index of the bucket

  2. Problem: The AWS console is slow and risky for bulk moves and deletes

    StorHelm's answer: Bulk operations by filter, with a match-count preview before confirming

  3. Problem: Cleanup and archiving depend on someone remembering

    StorHelm's answer: Scheduled tasks that run on an interval or daily at a set time

  4. Problem: Nobody knows what storage costs or where it goes

    StorHelm's answer: A dashboard with cost estimates and archiving-savings suggestions

  5. Problem: Sharing AWS keys with staff

    StorHelm's answer: Per-person logins and roles; AWS credentials stay encrypted in StorHelm

  6. Problem: No record of who moved or deleted what

    StorHelm's answer: A single Jobs log of every file-changing operation

02 — Bulk operations

Move a hundred thousand files, and keep working.

Every bulk action runs in the background. A preview shows how many files match before anything changes, and each job lands in one log.

  • Move, delete or change storage class by filter
  • Per-file failures are recorded instead of stopping the job
  • Every job records who started it, what moved and where
Illustration of the StorHelm Jobs log with sample data: recent move, delete, storage-class change, upload and Azure copy jobs, each with its status, file count and size.

Illustration with sample data.

03 — Automation

Cleanup that does not depend on someone remembering.

Schedule the routine work: delete, move or re-tier files older than a number of days, copy to Azure, or refresh the file index.

  • Run every N minutes, hours or days, or daily at a set time in your time zone
  • Tasks start disabled, with a file count preview and a Run now button
  • A per-run cap skips a run that would touch too many files
Illustration of the StorHelm Scheduled Tasks list with sample data: four tasks that archive, delete, copy to Azure or move files on a schedule, with each task's status and last run.

Illustration with sample data.

04 — Cost

Know what storage costs, and what archiving would save.

The dashboard totals your files, splits them by storage class and age, estimates the monthly cost and shows how much moving older data to a colder tier would save.

  • Storage by class and by age
  • Top folders and largest files
  • Cost rates default by AWS region and can be edited to match negotiated pricing
Illustration of the StorHelm Dashboard with sample data: total objects and size, storage split by class, an estimated monthly cost table, and a callout estimating the monthly saving from archiving older files.

Illustration with sample data.

05 — How it works

Connected in three steps.

  1. Connect a bucket with an IAM role

    Your cloud team applies a copy-paste CloudFormation or trust-policy template. StorHelm assumes the role; no keys change hands.

  2. StorHelm indexes it

    File names, sizes, dates and storage classes are indexed so search is instant. The files themselves never leave your bucket.

  3. Search, organize and automate

    Browse and search from the browser, run bulk operations with a preview, and put the routine work on a schedule.

06 — Security

Your bucket, your keys, your files.

StorHelm is built so that staff can work with files without holding AWS credentials, and so that the files stay where they are.

  • No AWS keys needed

    A cross-account IAM role with a unique External ID. No customer keys are stored.

  • Per-customer encryption

    Stored secrets are encrypted with per-customer keys and are never shown again after entry.

  • Files never pass through us

    Downloads and Azure transfers use short-lived signed links that expire after 15 minutes.

  • Every change is logged

    Each move, delete, upload and storage-class change is recorded in Jobs with who started it.

07 — Questions

Asked before the demo.

Do you store my files?

No. Files stay in your own bucket. StorHelm stores only file names, sizes, dates and storage classes, so it can search them.

Do you need my AWS keys?

No, not with an IAM role. StorHelm assumes a role in your AWS account using a unique External ID, so no keys are stored. Access keys are available as a quick start, and are encrypted at rest.

Which storage is supported?

Amazon S3 as the source. Azure Storage as a destination for copying or moving files.

How do I get an account?

Accounts are set up by the StorHelm team. Book a demo or contact us and we will create your organization and help you connect the first bucket.

See it on your own bucket.

Book a demo and we will connect a bucket together, index it, and walk through search, bulk operations and scheduling.