Change record status: 
Project: 
Introduced in branch: 
2.x
Introduced in version: 
2.0.0
Description: 

What Changed

Acquia Purge has been updated to use Acquia Cloud Platform's new purger infrastructure with JWT-based authentication. A new Acquia Platform One CDN Purger has been introduced that works with any CDN provider (Akamai, Fastly, Cloudflare, etc.), replacing the previous Fastly-specific purger.

Key changes:

  • New purger: AcquiaPlatformOneCdnPurger - Works with all CDN providers
  • Old purger: AcquiaPlatformCdnPurger - Limited to Fastly only
  • JWT authentication: Pi-Notary tokens used for secure API communication
  • Service identity configuration: New ACQUIA_SERVICE_IDENTITY_CONFIG environment variable

Environment Variable

AH_APPLICATION_UUID
ACQUIA_SERVICE_IDENTITY_CONFIG  # Path to JWT token file

On Acquia Cloud: These variables are automatically set. No action required.

JWT Token Configuration

The new purger uses Pi-Notary JWT tokens for authentication:

Token loading order:

  • Check for ACQUIA_SERVICE_IDENTITY_CONFIG environment variable - use specified path
  • Fallback to known default path if variable not set

On Acquia Cloud: JWT tokens are automatically configured. No manual setup needed.

Action Required

For All Sites - Add New Purger(if using Akamai, CloudFlare CDN provider):

The new Acquia Platform One CDN purger must be enabled to use the updated infrastructure:

  • Navigate to /admin/config/development/performance/purge
  • In the "Cache Invalidation" section, click "Add purger"
  • Select "Acquia Platform One CDN" from the list
  • Save configuration

Important: The new purger works with all CDN providers (Akamai, Fastly, Cloudflare, etc.), not just Fastly.

Migration from Old Purger:

If you're currently using the old "Acquia Platform CDN" purger (Fastly-only):

  • Add the new "Acquia Platform One CDN" purger (see steps above)
  • Test cache purging with the new purger
  • Once verified, you can remove the old "Acquia Platform CDN" purger
  • The old purger will continue to work but is deprecated

For Sites on Acquia Cloud:

✅ Environment variables are automatic - JWT tokens and application UUID are configured automatically.
Only action needed: Add the new purger at /admin/config/development/performance/purge.

Backward Compatibility: fully backward compatible.

Benefits

✅ Enhanced security - JWT-based authentication
✅ Better reliability - Improved purger infrastructure
✅ Platform alignment - Uses latest Acquia Cloud standards
✅ Zero config on Cloud - Automatic for hosted sites

Impacts: 
Site builders, administrators, editors
Module developers