Browse a bucket, upload any file, and manage objects in one place.
Credentials stay in memory · cleared on refresh| Name | Size | Last modified | Actions |
|---|
This folder is empty.
In the S3 console, open your bucket → Permissions → Cross-origin resource sharing (CORS), and paste this configuration to allow localhost development and saharan.dev.
[
{
"AllowedOrigins": [
"http://localhost:2345",
"https://saharan.dev"
],
"AllowedMethods": [
"GET",
"PUT",
"POST",
"DELETE",
"HEAD"
],
"AllowedHeaders": [
"*"
],
"ExposeHeaders": [
"ETag"
],
"MaxAgeSeconds": 3600
}
]IAM permissions: s3:ListBucket on the bucket; s3:GetObject (for overwrite checks), s3:PutObject, s3:DeleteObject, and s3:AbortMultipartUpload on the allowed prefix. KMS-encrypted buckets may require KMS permissions.
Delete asks for confirmation. In versioned buckets it creates a delete marker. This tool does not manage old versions. The path is a navigation boundary; IAM permissions enforce access.
Only bucket, region, and starting path are saved to localStorage. Credentials are never saved to localStorage, sessionStorage, cookies, URLs, or this site's server. Browser extensions and password managers are outside this page’s control.
AWS browser CORS documentation ↗