Amazon CloudFront now supports invalidation by cache tag

Amazon Web Services has introduced cache tag invalidation for CloudFront, its content delivery network service, allowing developers to remove groups of related cached content from edge locations using a single invalidation request. The new feature enables users to tag cached objects by including specified headers in HTTP responses with comma-separated tag values, then invalidate all objects sharing a particular tag simultaneously. This addresses a longstanding operational challenge where invalidating related content that didn't share common URL paths required tracking individual URLs or using broad wildcard patterns that could unnecessarily clear unrelated cached objects. The cache tag functionality is designed to streamline common workflows including updating product information across multiple pages, managing legal takedown requests, handling regulatory compliance requirements, and refreshing content on multi-tenant platforms. Site reliability engineers can configure header names through the CloudFront console, AWS CLI, or API, and assign multiple tags per object for granular cache management. AWS reports that invalidations now take effect in under 5 seconds at the 95th percentile, with end-to-end completion times under 25 seconds. The feature is available across all AWS regions where CloudFront operates, excluding China's Beijing and Ningxia regions. Each cache tag is priced as one path under AWS's existing invalidation pricing structure, providing organizations with a more efficient method to maintain high cache hit ratios while ensuring users receive updated content rapidly.