You can do so by binding a custom domain name. For more information, see Enabling Custom Origin Domain Name.
It depends on the following requirements:
The feature of configuring HTTPS for custom COS domain names is being upgraded. Currently, certificate hosting is supported in public cloud regions in the Chinese mainland, Singapore, and Silicon Valley, with more regions to come. For unsupported regions, you can configure a reverse proxy for the domain name by referring to Supporting HTTPS for Custom Endpoints.
COS currently does not support this feature. However, you can implement it by concatenating access links and using custom domain names to replace default domain names. For more information, see Regions and Access Endpoints.
If you use the COS v5 console and a JSON domain name is configured, the COS v5 console cannot display the new domain name. Check whether the domain name configured in your bucket is in JSON format, and if so, change it to an XML domain name.
Only one CNAME record can be configured for a domain name. Therefore, you need to delete the DNS relationship between the domain name and the Lighthouse instance first and then bind the domain name to the COS bucket.
After being configured, DNS resolution or CNAME may take several minutes to take effect. You can wait a while and try to access your bucket at your custom origin domain name again. If the problem persists, log in to your DNS console to check whether the DNS relationship is configured correctly.