S3-compatible storage setup — Framecho

01

Before you start

Create a dedicated bucket and scoped credentials, then open Framecho › Settings › Cloud › S3-compatible storage.

  1. Create a dedicated Framecho bucket and note its name and region.
  2. Create application credentials scoped to this bucket with upload, read, multipart, and delete permissions. Do not use root credentials.
  3. Choose private or public mode. Private mode needs no public bucket; public mode also needs a public object domain.
  4. Select Verify Connection. Framecho uploads, reads, and deletes a small test object.

Public read + permanent links

Links do not expire, but anyone with an object URL can read it. Allow public read only—never public write—and use a custom domain for share pages.

Never expose credentials.

Mask both the Access Key ID and Secret in screenshots and support tickets. Use a separate bucket-scoped key and revoke it immediately if exposed.

02

Map fields into Framecho

With a built-in provider, enter only the region and Framecho builds the endpoint. Enter an endpoint manually only for Custom.

ProviderChoose the matching preset; use Custom for Qiniu, MinIO, and other services.
RegionThe provider Region ID, such as cn-hongkong, ap-shanghai, or us-east-005—not its display name.
EndpointThe public S3 API service address, not a console or CDN URL. Presets generate it automatically.
BucketThe complete bucket name; Tencent COS includes the APPID suffix.
Access Key ID / SecretThe provider AK/SK, SecretId/SecretKey, or keyID/applicationKey pair.
Bucket accessPrivate with an expiry is recommended.
Public domainPublic mode only: the HTTPS root that directly serves objects, with no object path.
Path prefixDefaults to framecho; all uploads are stored below it.
Create share pagesCreates HTML previews with media, captions, Framecho icon, and favicon.

Choose your provider

OSS
03

Alibaba Cloud OSS

Use a RAM user AccessKey. Keep the bucket private; public HTML pages need a custom domain to open in a browser.

  1. Create an OSS bucket and copy its Region ID.
  2. Create a dedicated RAM user and AccessKey scoped to object read, write, and delete in the bucket.
  3. Choose Alibaba Cloud OSS in Framecho and enter the region, bucket, AccessKey ID, and AccessKey Secret.
  4. Use Private and verify. Configure public read only when permanent public URLs are required.
Regioncn-hongkong
Bucketyour-bucket
Access Key IDRAM AccessKey ID
Secret Access KeyRAM AccessKey Secret
Note

OSS forces HTML to download on its default domain. Use a custom domain in Public mode for browser share pages; never enable public write.

Open provider documentation
COS
04

Tencent Cloud COS

COS maps CAM SecretId and SecretKey to S3 credentials. Bucket names normally include the APPID.

  1. Create a COS bucket and copy its Region ID and full name including APPID.
  2. Create a scoped CAM user/key with object read, write, and delete permissions.
  3. Choose Tencent Cloud COS; put SecretId in Access Key ID and SecretKey in Secret Access Key.
  4. Use private expiring links, or grant anonymous read and enter a public domain.
Regionap-shanghai
Bucketexample-1250000000
Access Key IDSecretId
Secret Access KeySecretKey
Note

COS default domains may force HTML downloads. For browser share pages, use an approved custom or CDN domain in Public mode.

Open provider documentation
R2
05

Cloudflare R2

R2 needs your Account ID and R2-specific API token credentials—not a general Cloudflare API token.

  1. Create an R2 bucket.
  2. Under Manage API Tokens, create an Object Read & Write token scoped to the bucket.
  3. Save the one-time Secret Access Key, Access Key ID, and your Cloudflare Account ID.
  4. Choose Cloudflare R2 in Framecho, fill all fields, and verify.
Account IDCloudflare Account ID
Regionauto
Access Key IDR2 Access Key ID
Secret Access KeyR2 Secret Access Key
Note

For public mode, attach a custom domain. r2.dev is rate-limited and intended for development. Private mode does not need Public Development URL.

Open provider documentation
B2
06

Backblaze B2

Create a standard Application Key. The Master Application Key does not work with the S3-compatible API.

  1. Copy the bucket Endpoint and its region, such as us-east-005.
  2. Under Application Keys, create a standard key with read/write access to the bucket.
  3. Put the 25-character keyID in Access Key ID and the one-time applicationKey in Secret Access Key.
  4. Choose Backblaze B2, enter region and bucket, and verify.
Regionus-east-005
Bucketyour-bucket
Access Key ID25-character keyID
Secret Access KeyapplicationKey
Note

Do not enter the 12-character account/master ID, bucket ID, or key name. The region must exactly match the bucket Endpoint.

Open provider documentation
AWS
07

Amazon S3

Use long-term access keys for a dedicated IAM principal scoped to the Framecho bucket and prefix.

  1. Create an S3 bucket and note its Region.
  2. Create an IAM identity/key with Put/Get/Delete, ListBucket, and multipart permissions on the bucket.
  3. Choose Amazon S3 and enter Region, Bucket, Access Key ID, and Secret Access Key.
  4. Keep Block Public Access enabled and use private expiring links.
Regionap-east-1
Bucketyour-bucket
Access Key IDIAM Access Key ID
Secret Access KeyIAM Secret Access Key
Note

Never use AWS root credentials. Public mode requires deliberate Block Public Access and read-only bucket-policy changes and is riskier.

Open provider documentation
S3
08

Qiniu, MinIO, and other S3 services

Any HTTPS SigV4 service supporting PUT, multipart upload, GET, and batch delete can be tested.

  1. Copy the public S3 API endpoint and signing region from the provider.
  2. Choose Custom and enter the full HTTPS endpoint, region, bucket, and credentials.
  3. Select virtual-hosted or path-style addressing as required; MinIO often uses path-style.
  4. Run verification and use the service only after upload, read, and delete all pass.
Endpointhttps://s3.example.com
Regionus-east-1
Path-styleAs required
CredentialsS3 Access Key / Secret Key
Note

For Qiniu Kodo, use the S3 public endpoint shown in the bucket overview; the Region is the region segment in that endpoint.

Open provider documentation
09

Troubleshooting

SignatureDoesNotMatch

The secret, region, endpoint, or system clock differs. Recopy credentials and use the region of the same bucket.

NoSuchBucket

Bucket name and region do not match. For Tencent COS, include the APPID suffix.

InvalidAccessKeyId

The wrong credential type or field was used. B2 requires the 25-character keyID of a standard Application Key.

NSURLErrorDomain -1003

The endpoint hostname does not resolve. Check for a console URL, private endpoint, bucket domain, typo, or bad region.

Link downloads instead of opening

OSS/COS default-domain policy or the file type can force downloads. Use a custom domain in Public mode for browser HTML pages.

Upload passes but read fails

The key can write, but the bucket/domain cannot read, or the public domain points at another bucket.

Run verification once more

After all three checks pass, uploads go straight to your bucket and credentials remain in the macOS Keychain.

Review field mapping