# Purge CDN Cache

<figure><img src="/files/GcNYsNRLjkKxnuRGHj3a" alt=""><figcaption></figcaption></figure>

This feature allows admins to purge CDN caches at various scopes:

* The entire planet
* Specific domain(s) within the planet
* Specific paths within domain(s)&#x20;

A history of current and past activity is provided.

## Prerequisites

This feature is available when at least one CDN has been set up in the system. (To do this, contact customer support.) If no CDN is currently configured, an error message will be shown.

## **Three-Step Purging Process**&#x20;

Purging requires these steps:

1. Select the cache(s)
2. Initiate the purge
3. (Optional) monitor the results

## **Step 1: Select the cache(s) to purge**&#x20;

Cache selection varies, depending on the CDN being used.

### **To purge caches for an entire planet**&#x20;

For non-AWS CDNs, at the top left of the page, ensure that **All domains in the planet** is selected, then skip the remainder of Step 1, and continue to Step 2 below.

### **To purge one or more domains within the planet**&#x20;

AWS Cloudfront users will see the controls described below. For non-AWS CDNs, at the top left of the page, ensure that **Specific domains** is selected to display them.

* **Select CDN**: If there are multiple AWS load balancers, this control will appear. Select the AWS CDN provider for each domain/path where the cache has to be purged. \
  \
  In other situations (e.g., the planet uses the Google Cloud or Link11 CDN, or has only one AWS load balancer) this control is unnecessary and will not appear.
* **Alternative domain names**: For non-AWS CDNs, specify a domain configured within the planet. AWS Cloudfront does not support individual purges, so Cloudfront users will see a non-editable list (for informational purposes only) of all the domains for which caches will be purged.
* **Add a specific path**:
  * When this control is untoggled, caches for the entire domain will be purged.
  * When this control is toggled, the **Path** field will appear. Enter the path for which the cache should be purged.

**Adding more domains/paths**\
Multiple domains and/or paths can be specified for a purge.

After appropriate values have been entered into the controls described above, if another domain or path purge needs to be defined, select the **New Host** button and populate the new entry in the purge list. Repeat this process until all desired purges have been specified.

## Step 2: Initiate the purge

Select the **Purge CDN cache** button. The specified purge(s) will appear in the **Results** list at the bottom of the page.

## Step 3: (Optional) monitor the results

The **Results** list shows a history of purge commands submitted during the previous week. The list shows the date and time when each was submitted.

Within the list, the **Status** field shows the result of each purge during the most recent status update. Updates occur when the page is loaded or reloaded, and also each time the **Refresh Status** button is selected.

The possible statuses are:

* **In progress**: as of the most recent status update, the purge was still being processed. (Note that depending on how recently the list was updated, the actual current status might be different.)
* **Done**. The purge completed successfully.
* **Failed**. The purge was attempted but was not successful. To try again, a new purge command must be submitted.
* **Not available**. The purge was unsuccessful because the CDN was unavailable. To try again, a new purge command must be submitted.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://waap.docs.link11.com/console-walkthrough/system/purge-cdn-cache.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.