"InvalidArgument: The parameter MinTTL is required" for older serverless-nextjs versions (1.16 and below)
See original GitHub issueDescribe the bug
Deployments suddenly broke for older version 1.16 and below and throws InvalidArgument: The parameter MinTTL is required.
Recent changes to TTL may caused that as serverless-nextjs might pick latest aws-cloudfront version
To Reproduce
deploy any simple website with almost zero config with @sls-next/serverless-component@1.16.0
Expected behavior
Expect to not throw
Desktop (please complete the following information):
- OS: MacOS and Linux tested
- Serverless-nextjs version:
@sls-next/serverless-component@1.16.0
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:22 (5 by maintainers)
Top Results From Across the Web
InvalidArgument error on Cloudfront createDistribution
When i put the MinTTL on the DefaultCacheBehaviour field, it says that ForwardedValues is required, which is another deprecated property. I am ...
Read more >Serverless Next.js Component - Serverless Framework: Plugins
Pages that need server side compute to render are hosted on Lambda@Edge. The component takes care of all the routing for you so...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@himynameistimli for now I published
@sls-next/serverless-component@1.15.0-patch.0
(which is 1.15.0) with exact dependencies (https://www.npmjs.com/package/@sls-next/serverless-component/v/1.15.0-patch.0) so it should resolve this issue. Let me know if this works.@Bryceacampbell Please try latest 1.17.0 version (not alpha), as mentioned above there was a dependency versioning issue that caused old component versions to pull newer dependency versions. Unfortunately we can’t republish older versions to npm 😦