Skip to main content

Expiration of files set in GCS and S3

When calling the URL of GCS or S3 files saved from Kuroco through APIs like Topics::list/details, a URL with an expiration date is returned in the response. This is to ensure the continuity with the content. please be aware that if you use this URL for a long time in tools like SSG, it may expire.

The expiration periods for each scenario are set as follows:

GCS/S3 files associated with content​

GCS/S3 files associated with content are obtained through APIs such as Topics::list/details/preview to get the file URL. This will be the expiration time for those files.

  • If the API has a cache period set within 7 days
    => API cache period + 30 seconds
  • If the API has a cache period set for more than 7 days
    => 7 days
  • If the API does not have a cache period set
    => 30 minutes or the shorter of the session time + 30 seconds
caution

There is a risk of expiration if you use this URL for a long time in tools like SSG.

GCS/S3 files in the file manager​

The URLs for files saved in the GCS/S3 directory from the File Manager will have the following expiration period.

  • When files from a restricted access folder are obtained via API
    Similar to GCS/S3 files associated with content
  • When files from a restricted access folder are opened from the file path in the file manager
    => 30 minutes or the shorter of the session time + 30 seconds
  • Public folder
    => Unlimited

URL used for display in the admin panel​

The URLs for GCS/S3 files displayed in the content editing screen, content detail screen of the approval workflow, and form submissions have the following expiration period.

=> 30 minutes or the shorter of the session time + 30 seconds

info

Since the file URL is updated with each access, there is no impact on normal admin panel usage.

Support

If you have any other questions, please contact us or check out Our Slack Community.

Contact form
Join Kuroco Slack community