aws-amplify / aws-amplify/amplify-hosting

[Feature request] Ability to manually purge cached pages/urls

Open
#314 7 comments 7 reactions 0 assignees View on GitHub
feature-request hosting
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**
According to [this comment](https://github.com/aws-amplify/amplify-console/issues/178#issuecomment-537616693) from AWS it's a *feature* that deleted files don't get purged from the cache until after several more builds. This can present problems for some (possibly even legal ones). I'm opening this up as a feature request, since it seems all the other issues relating to this are getting closed because it's a feature, not a bug.

**Describe the solution you'd like**
Either via UI or through a configuration file/setting/api (preferably all of the aforementioned ways) a way to purge specific urls, or even the entire cache. It could even be a build-time setting. Cloudfront has UI and APIs for this, though not instant, it'd probably be acceptable.

**Additional context**
Related issues: #74, #178, #294

Contributor guide

Open the contributing guide

Research direction

Start by reviewing related issues #74, #178, and #294 plus the linked AWS comment, then compare the CloudFront invalidation UI and API options mentioned in the request. Done means users can purge selected URLs or the entire cache through an agreed supported interface, with behavior documented and verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.