Hi Pulumi team, I’m encountering an issue with setting a custom timeout on an AWS API Gateway integration. AWS Support has extended my timeout limit to 180,000 ms as an exception, but when I try to set this timeout using Pulumi’s

aws.apigatewayv2.Integration

resource, Pulumi throws an error stating that the timeout must be between 50 ms and 30,000 ms. I've confirmed the increased timeout with AWS Support, and they recommended I update my infrastructure to reflect this. It seems that Pulumi is validating the timeout based on the default limits, not the updated configuration. Could you advise on how to bypass or override this validation in Pulumi, or if there's an alternative approach to set the timeout to 180,000 ms directly within Pulumi? Thanks in advance for any guidance!

I just double checked our code and there's no validation done for the timeout of

apigatewayv2.Integration

. Can you try setting that timeout via the AWS CLI or API to confirm the limit increase has been applied to your account? I'm a bit surprised that they actually performed a limit increase here because they mentioned in their docs that the integration timeout cannot be changed: https://docs.aws.amazon.com/apigateway/latest/developerguide/limits.html

yes I checked, as you can see it

Could it be that they increased the limit for REST APIs? I.e. API Gateway V1? That one allows changing the timeout

I am using API Gateway V2 for HTTP API

But that quota only applies to Rest APIs. You can see that in the quota and limits docs here: https://docs.aws.amazon.com/apigateway/latest/developerguide/limits.html#api-gateway-execution-service-limits-table HTTP and Websockets APIs do not allow raising the integration timeout, only the REST API does

thanks