Cloud

S3 URI / URL Parser

Convert freely between s3:// URIs, virtual-hosted URLs, path-style URLs, and S3 ARNs. Pull the bucket, key, region, and version ID out of any form, and get ready-to-run aws-cli commands for copying or listing.

Résumé de l'outil

Cet outil accepte une entrée structurée et renvoie une sortie déterministe dans le navigateur, sans envoi au serveur.

Nom de l'outil: S3 URI / URL Parser
Intention d'entrée: Fournissez le contenu source à transformer, valider ou analyser.
Intention de sortie: Recevez une sortie normalisée prête à être copiée, réutilisée ou déboguée.
Entrée d'exemple: https://my-bucket.s3.us-east-1.amazonaws.com/reports/2025/q1.csv
Sortie d'exemple: bucket=my-bucket · key=reports/2025/q1.csv · region=us-east-1 · s3://my-bucket/reports/2025/q1.csv

Local processing / privacy notice

Inputs are processed in your browser session.
We do not send raw input/output values to our analytics endpoint.
Use reset/clear actions when working with confidential data.

Parsed entirely in your browser.

S3 URI, URL, or ARNDrop file

Examples:

Bucket: my-bucket
Key: reports/2025/q1.csv
Region: us-east-1
Addressing: Virtual-hosted HTTPS

s3:// URI

s3://my-bucket/reports/2025/q1.csv

HTTPS URL

https://my-bucket.s3.us-east-1.amazonaws.com/reports/2025/q1.csv

aws s3 cp

aws s3 cp s3://my-bucket/reports/2025/q1.csv ./

aws s3 ls

aws s3 ls s3://my-bucket/reports/2025/q1.csv

Introduction à l'outil

Vue d'ensemble de l'outil

S3 exposes the same object under several addressing schemes: s3://bucket/key for the CLI, https://bucket.s3.<region>.amazonaws.com/key for virtual-hosted access, https://s3.<region>.amazonaws.com/bucket/key for legacy path-style, plus arn:aws:s3:::bucket/key for IAM. Each has slightly different rules around region segments, dualstack, and Transfer Acceleration. This tool normalizes them all: paste any form, get the others, and see warnings if the bucket name would fail S3 DNS rules.

Cas d'usage

Convert a console URL into an s3:// URI for the CLI
Pull the bucket and key out of a messy pre-signed URL (minus the signature)
Validate that a bucket name still obeys S3 DNS rules after a rename
Generate a quick "aws s3 cp" command from a URL you were given

Exemples d'entrée/sortie

Intention d'entrée

https://my-bucket.s3.us-east-1.amazonaws.com/reports/2025/q1.csv

Intention de sortie

bucket=my-bucket · key=reports/2025/q1.csv · region=us-east-1 · s3://my-bucket/reports/2025/q1.csv

Intention d'entrée

s3://videos/intro.mp4

Intention de sortie

bucket=videos · key=intro.mp4 · region=—

Questions fréquentes

What are virtual-hosted and path-style URLs?+

Virtual-hosted URLs put the bucket in the hostname (bucket.s3.region.amazonaws.com). Path-style URLs put it in the path (s3.region.amazonaws.com/bucket). AWS is phasing out path-style for new buckets.

Does this work on pre-signed URLs?+

Yes — the parser will extract the bucket, key, and region. The signature query parameters are surfaced for reference but not validated.

What are the S3 bucket naming rules?+

3–63 characters, lowercase letters, numbers, dots, and hyphens; must start and end with a letter or number; no adjacent dots; not an IP address. The tool flags names that violate these rules.