Can I set the URL of a private object to never expire? - Object Storage Service

No. Signed URLs for private objects always include a validity period — there is no option to make them permanent.

The sum of the current Unix timestamp and the signed URL's expiration time cannot exceed 9223372036854775807 (the maximum value of a 64-bit signed integer). If the sum exceeds this limit, OSS returns an error.

To find the maximum expiration time, subtract the current Unix timestamp from 9223372036854775807. For example, if the current timestamp is 1643341269, the expiration time cannot exceed 9223372035211434538 seconds.

Workaround (not recommended)

If your use case requires a URL that does not expire, you can set the object's access control list (ACL) to public-read. This removes the need for a signed URL, because the object becomes publicly accessible without authentication.

Warning

Setting an object ACL to public-read makes the object accessible to anyone with the URL, with no authentication required. Any person or system that obtains the URL can read the object. Use this option only when the content is intended for unrestricted public access, and never for sensitive or private data.

For more information on object access permissions, see Object ACLs.