Skip to content

Commit

Permalink
Add docs for purging the standby CDN's cache
Browse files Browse the repository at this point in the history
  • Loading branch information
robinjam committed Jan 24, 2024
1 parent fbdb5a8 commit de89d91
Showing 1 changed file with 19 additions and 0 deletions.
19 changes: 19 additions & 0 deletions source/manual/purge-cache.html.md
Expand Up @@ -68,6 +68,25 @@ production.
"Purge all".
1. The UI will ask you for confirmation before issuing the purge request.

## Purge a page from the standby CloudFront CDN

In addition to our primary CDN (Fastly), we also have a standby CDN set up on
CloudFront. This standby CDN is only intended to be used during a Fastly
outage, so there's a limited number of situations in which you would need to
purge its cache.

If an item urgently needs to be removed from the cache, you can create an
invalidation from the AWS console.

1. Log into the AWS console with `gds aws govuk-production-poweruser -l`.
1. Under the [CloudFront distributions page](https://us-east-1.console.aws.amazon.com/cloudfront/v4/home?region=eu-west-1#/distributions),
choose the appropriate distribution: `WWW` for www.gov.uk or `Assets` for assets.publishing.service.gov.uk.
1. Select the "Invalidations" tab, and click "Create invalidation".
1. Enter the full paths of all resources to purge (that is, everything after
the hostname in the URL). You can optionally use wildcards (`*`). To purge
all objects, enter the path `/*`.
1. Click "Create invalidation".

## Further reading

See [Fastly's documentation on purging](https://developer.fastly.com/learning/concepts/purging/).
Expand Down

0 comments on commit de89d91

Please sign in to comment.