Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Cloud CDN
  • Getting started
    • All guides
      • Creating a resource
      • Copying configuration from one resource to another
      • Updating basic settings of a resource
      • Getting information about a resource
      • Configuring resource caching
      • Configuring log export
      • Prefetching files to CDN servers
      • Purging resource cache
      • Configuring request and response headers
      • Configuring CORS for responses to clients
      • Configuring HTTP methods
      • Enabling file compression
      • Enabling file segmentation
      • Enabling origin shielding
      • Configuring request redirection
      • Setting up access via a secure token
      • Setting up location rules
      • Managing additional resource settings
      • Disabling a resource
      • Managing resource labels
      • Deleting a resource
      • Viewing resource statistics
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics for the EdgeCDN provider
  • Monitoring metrics for the Yandex Cloud CDN provider
  • Audit Trails events
  • Release notes
  • Troubleshooting
  1. Step-by-step guides
  2. Resources
  3. Purging resource cache

Purging the resource cache

Written by
Yandex Cloud
Updated at December 3, 2025

To purge the cache of the resource:

Management console
CLI
API
  1. In the management console, select the folder where your resource is located.

  2. Go to Cloud CDN.

  3. Click the resource name.

  4. Navigate to the Content tab.

  5. In the top-right corner, click Purge cache.

  6. Select the type of cache purging:

    • Full: To purge the cache for all files.

    • Selective: To purge the cache for selected files. In the File path field, specify comma-separated paths to the files.

      For partial purging, you can specify paths to individual files and folders. Each path must begin with the / or (only when using the EdgeCDN provider) * character. The * wildcard character can replace any number of characters.

      Note

      When using the Yandex Cloud CDN provider, you can only specify the * wildcard character at the end of the path. If you specify * at the beginning or middle of a path, the cache for matching files will not be purged.

  7. Click Purge cache.

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

  1. View the description of the CLI command to update a resource:

    yc cdn resource update --help
    
  2. Get a list of all CDN resources in the default folder:

    yc cdn resource list --format yaml
    

    Result:

    id: s0me1dkfjq********
    folder_id: s0mef01der7p********
    cname: testexample.com
    created_at: "2022-01-19T09:23:57.921365Z"
    updated_at: "2022-01-19T10:55:30.305141Z"
    active: true
    options:
      edge_cache_settings:
        enabled: true
        default value: "345600"
      cache_http_headers:
        enabled: true
        value:
        - content-type
        - content-length
        - connection
        - server
        - date
        - test
      stale:
        enabled: true
        value:
        - error
        - updating
      allowed_http_methods:
        value:
        - GET
        - POST
        - HEAD
        - OPTIONS
    origin_group_id: "89783"
    origin_group_name: My origins group
    origin_protocol: HTTP
    ssl_certificate:
      type: DONT_USE
      status: READY
    
  3. Purge the file cache:

    yc cdn cache purge \
      --resource-id <resource_ID> \
      --path <file_path_1>,<file_path_2>,...,<file_path_n>
    

    Where:

    • --resource-id: ID of the CDN resource to purge cache in.

    • --path: List of paths to CDN resource files whose cache needs purging.

      For partial purging, you can specify paths to individual files and folders. Each path must begin with the / or (only when using the EdgeCDN provider) * character. The * wildcard character can replace any number of characters.

      Note

      When using the Yandex Cloud CDN provider, you can only specify the * wildcard character at the end of the path. If you specify * at the beginning or middle of a path, the cache for matching files will not be purged.

      If the CDN resource uses Vary headers (e.g., Vary: Accept-Encoding), you must add the * wildcard character to the end of the path when purging the cache to remove all possible cached versions of the files, e.g., /image/foobar.png*.

      If you omit the --path setting with paths to files, the cache of all resource files will be purged. For more information, see Purging cache.

    For more information about the yc cdn cache purge command, see this CLI reference.

Use the purge REST API method for the Cache resource or the CacheService/Purge gRPC API call.

It may take up to 15 minutes to purge the cache.

Was the article helpful?

Previous
Prefetching files to CDN servers
Next
Configuring request and response headers
© 2025 Direct Cursus Technology L.L.C.