How to set individual TTL times (Min TTL, Max TLL, Default TTL)?

[mattdell]

Following the docs in the Readme there is a section about how to set the ttl

myNextApplication:
  component: serverless-next.js
  inputs:
    cloudfront:
      # this is the cache behaviour for next.js api pages
      api:
        ttl: 10

Cloudfront actually has the options for setting min, max, and default ttl times in the UI:

How would I go about setting the Max TTL only to 31536000?

It seems this was supposed to be fixed in PR #282 since it enables "all cloudfront inputs" but these are missing. Looking through the code, it seems to be a limitation in aws-cloudfront inputs

See how it takes in ttl and then assigns that to min, max, and default? https://github.com/serverless-components/aws-cloudfront/blob/master/lib/getCacheBehavior.js

I have raised an issue there but it doesn't appear to be very active.

Does anyone else have this problem?

[medv]

Yeah this is relevant to us as well. I was meant to put some time into this when I have a chance but haven't had the opportunity yet. It's still on my list (that's currently still growing from the other end, ouchie)

[dphang]

I came across this problem while working on: #581. It looks like even for default CloudFront behaviors, min, max and default TTLs are all the same. This inflexibility is also causing issues for static files, e.g default, min, max TTL are all set to 86400 (1 day), so actually our Cache-Control headers of 31 days / 365 days is really only 1 day.

I am working on a fix this week for this and also allowing to set min, max, default TTLs independently. Luckily, aws-cloudfront component was already copied into this package, so we can make changes ourselves. As you noted, that repository under serverless-components doesn't seem active.

[dphang]

PR is merged and the latest published alpha should have this, so I'm closing this thread. Please let us know if there are any other issues.