I found here a warning about presigned URLS and CND:
Using presigned URLs does not allow transferred files to be cached when using the Spaces CDN. Attempting to do so may result in double the bandwidth charge without the CDN’s performance benefit.
from below link:
https://docs.digitalocean.com/products/spaces/how-to/use-aws-sdks/
and also found anther description here:
You can also use presigned URLs with the Spaces CDN. To do so, configure your SDK or S3 tool to use the non-CDN endpoint, generate a presigned URL for a GetObject request, then modify the hostname in the URL to be the CDN hostname (
<space-name>.<region>.cdn.digitaloceanspaces.com, unless the bucket uses a custom hostname).
from below link:
https://docs.digitalocean.com/products/spaces/how-to/enable-cdn/
These two descriptions make me confused, whether the presigned URLs can work with CDN or not?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Heya,
By default, presigned URLS do not use the CDN hostname — they use the standard (non-CDN) endpoint.
If you use a presigned URL directly from the non-CDN endpoint, the CDN is bypassed, no caching, and you pay full bandwidth from the origin.
Regards
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.