CDN cache purge is a data purge feature provided by COS based on the SCF service. It can automatically purge the data cached on CDN edge nodes. After you add a trigger rule for a bucket, when a file is updated to the bucket, the SCF function preconfigured by COS will be automatically triggered to purge the cached data.
- If you added a cache purge rule for your bucket in the COS console, the resulting purge function will also appear in the SCF console. Do not delete this function; otherwise, your rule may not take effect.
- Regions where SCF is available support CDN cache purge, including Guangzhou, Shanghai, Beijing, Chengdu, Hong Kong (China), Singapore, Mumbai, Toronto, and Silicon Valley. For more supported regions, see Serverless Cloud Function.
- CDN cache purge may fail due to factors such as unstable network connection. In these cases, you can click View Log for the function created in the COS console to enter the SCF console and view the error log details for troubleshooting.
- The CDN cache purge feature depends on the SCF service, which provides a free tier. Excessive usage will be billed at SCF prices. For more information, see Pricing. For this feature, the more often you purge the cache, the more invocations you will need to use.
If you haven't activated SCF, go to the SCF console to activate it and authorize the service as instructed.
PUTas the event type, only uploads through the
PUT ObjectAPI can trigger the function to purge the cache on CDN edge nodes.
PurgeUrlsCache. In this way, SCF can replace your CDN cache with the latest data CDN pulls from the COS origin.