Description

CloudFront defines a default limit of 60 seconds for response timeout in http origin configurations. The library follows this default limit by validating the readTimeout attribute in HttpOriginProps and constraining the value between 1 and 60 seconds.

This is a soft limit and a limit increase is possible: in such a case the origin configuration should allow setting this value to a bigger value, up to the service quota's hard limit (afaik 180 seconds).

Use Case

Our company requested and obtained a limit increase for our load balancer origin configuration value up to 180 seconds, but there is no way to set this value through the LoadBalancerV2Origin construct in our distribution's stack.

Proposed Solution

We should make it possible to exceed this maximum value, by providing a bigger range and documenting that values over 60 seconds are possible only after a limit increase request in the target account or by providing some other mechanisms such as a feature flag or another attribute in the configuration interface.

Other information

The only possible solution that I see now as a workaround is to access the low level construct node and override the property with a custom value, but I had no chance to give it a try.

Acknowledge

• I may be able to implement this feature request
• This feature might incur a breaking change