Alibaba Cloud OSS exposes an S3-compatible API with AWS Signature V4 against https://s3.oss-<region>.aliyuncs.com. MIRAGE derives this endpoint from your region automatically.
Credentials (RAM AccessKey ID and AccessKey Secret) are created the same way in both runtimes, see Alibaba OSS Credentials.
Node (server-side)
Browser (presigned URLs)
The browser AliyunResource is secret-free, your backend signs each operation using your RAM keys and returns a URL. OSS’s S3-compatible endpoint accepts AWS Signature V4, so @aws-sdk/s3-request-presigner works, pointed at the OSS endpoint.
1. Server: sign URLs with the OSS endpoint
2. Browser: wire it up
region on the browser config is only used for display/logging; the actual endpoint is baked into the presigned URLs your backend returns.
3. CORS
Configure CORS rules in the Alibaba Cloud console: OSS -> your bucket -> Content Security -> CORS. Allow your dev/production origins with methods GET, PUT, HEAD, DELETE, POST, allowed headers *, and expose headers ETag, Content-Length, Content-Type, Last-Modified.
See the Alibaba OSS resource docs for the equivalent Python wiring.