How do we invalidate the cache in AWS CloudFront CDN when publishing content?

Environment

AEM 6.0-6.3

Steps

There is nothing out-of-the-box in AEM that does this. However, a custom solution could be developed:

  1. Implement a custom replication agent. See the steps here.
  2. To do the actual cache invalidation in the TransportHandler code, use the CloudFront API POST invalidation as documented here.

Alternatively, instead of creating a flush agent, the best practice is simply to leverage the "Cache-Control: max-age=..."  header to control the TTL of files in the CloudFront CDN.  This works instead of implementing a replication agent to invalidate the CloudFront cache. See this documentation.

Esta obra está autorizada con arreglo a la licencia de Reconocimiento-NoComercial-CompartirIgual 3.0 Unported de Creative Commons.  Los términos de Creative Commons no cubren las publicaciones en Twitter™ y Facebook.

Avisos legales   |   Política de privacidad en línea