如何将多个静态页面归入单个CloudFront行为？解决配额不足问题

Short answer: No. CloudFront only allows one path pattern per behavior—you can't list multiple distinct paths (like /page-1 and /page-2) in a single behavior configuration. Your initial thought that this isn't directly possible is correct.

When dealing with a growing number of static pages, these approaches will help you keep your CloudFront configuration clean and within quota:

1. Restructure content into shared directories #

If you have control over your content's URL structure, move similar pages into a common parent directory. For example, relocate /page-1 and /page-2 to /static-pages/page-1 and /static-pages/page-2. Then create one behavior with the path pattern /static-pages/* to apply your desired cache settings to all of them at once. This is the simplest and most maintainable solution if you can adjust your URLs.

2. Use CloudFront Functions for path-specific rules #

Create a single behavior that covers a broad range of paths (like /*), then attach a CloudFront Function to handle path-based cache adjustments. The function can check if the request URI matches /page-1 or /page-2 and apply your custom cache policy for those paths, while using default settings for everything else. CloudFront Functions are fast, cheap, and perfect for simple logic like this.

Example snippet of a CloudFront Function (simplified):

function handler(event) {
    const request = event.request;
    const uri = request.uri;
    
    // Apply custom cache settings for specific pages
    if (uri === '/page-1' || uri === '/page-2') {
        request.headers['cache-control'] = { value: 'max-age=3600' };
    }
    
    return request;
}

3. Use Lambda@Edge for advanced scenarios #

If you need more complex logic (like combining path checks with query parameters, origin routing, or dynamic content), use Lambda@Edge. Attach a function to the viewer-request or origin-request event of a broad behavior, then apply custom rules based on the request path. This is more flexible than CloudFront Functions but has slightly higher latency and cost.

4. Consolidate behaviors with identical settings #

If multiple behaviors use the exact same cache policy, origin settings, and other configurations, replace them with a single behavior using a wildcard or prefix pattern that covers all those paths. For example, if /page-3, /page-4, and /page-5 all share the same rules, use /page-* as the path pattern (if the naming allows) or restructure them into a shared directory.

5. Request a quota increase (last resort) #

If none of the above options work for your use case, you can submit a quota increase request via the AWS Support Center. Keep in mind this is a temporary fix—long-term, consolidating behaviors will make your configuration easier to manage.

内容的提问来源于stack exchange，提问作者alexmcfarlane