Cloud Storage
Rewrite mixed S3 bucket refs to one address style
Normalize mixed S3 bucket references into one address format.
Go · MIT license
overview
What s3reverse does
s3reverse rewrites a messy list of S3 bucket references into one shape. Recon dumps mix bare names, path-style URLs, and virtual-hosted hostnames; that mix breaks dedupe and scanners. Feed the list with -iL and pick a single target format.
Choose -tN for bare names, -tS for s3 URLs, -tP for path style (s3.amazonaws.com/bucket), or -tV for virtual-hosted (bucket.s3.amazonaws.com). Write lines with -oN or an array with -oA. Optional -verify checks whether each reference is reachable while converting.
In a Trickest Cloud Storage workflow, place it between bucket discovery and a scanner such as s3scanner so every candidate arrives in the format the next node expects. It converts and optionally verifies; it does not dump objects.
source github.com/hahwul/s3reverse
use cases
Where s3reverse fits
Normalize mixed bucket references
Convert a list that mixes names, path-style URLs, and virtual-hosted hostnames into one format so duplicates collapse and downstream tools parse cleanly.
Prepare input for a bucket scanner
Emit bucket names or s3 URLs in the exact shape a scanner like s3scanner expects, so the discovery-to-scan handoff is clean.
Verify access during conversion
Enable -verify to check bucket access as the list is normalized, flagging which references resolve.
Pick path or virtual-hosted style
Choose -tP or -tV output to match the addressing convention the rest of the pipeline relies on.
reference
s3reverse inputs and flags
| Name | Type | Flag | Description |
|---|---|---|---|
| input-list | FILE | -iL | Input list of bucket references. |
| to-name-format | BOOLEAN | -tN | Convert to name format (example: github-cloud). |
| convert-to-s3-url | BOOLEAN | -tS | Convert to s3 URL. |
| convert-to-path-style | BOOLEAN | -tP | Convert to path style (example: https://s3.amazonaws.com/github-cloud). |
| convert-to-virtual-hosted-style | BOOLEAN | -tV | Convert to virtual-hosted style (example: github-cloud.s3.amazonaws.com). |
| verify-bucket-access | BOOLEAN | -verify | Verify bucket access. |
| output-format-normal | BOOLEAN | -oN | Write output in normal format. |
| output-format-array | BOOLEAN | -oA | Write output in array format. |
Showing key inputs. s3reverse exposes 8 inputs in total.
example
Run s3reverse
# normalize mixed bucket refs to bare names
s3reverse -iL buckets.txt -tN -oNexample-assets
example-logs
example-backups
example-static
example-uploads
example-cdn
example-terraform-state
example-ci-artifactsguidance
Choosing s3reverse
Use s3reverse when S3 bucket references arrive in mixed formats and you need one consistent shape before scanning. It does not scan or dump buckets; pair it with s3scanner. For discovering candidates, use cloud_enum or lazys3.
s3scanner
Finds open S3 buckets and dumps contents; the scanner s3reverse prepares input for.
cloud_enum
Enumerates cloud storage across AWS, Azure, and GCP to discover candidate buckets.
lazys3
Brute-forces S3 bucket names from permutations to surface new candidates.
faq
s3reverse questions
Run s3reverse yourself
A mixed bucket list feeds s3reverse, which normalizes every reference into one format and hands it to s3scanner before results land as a queryable output.
Facts on this page come from the live Trickest tool library.