A simple lambda function to test if we can invoke a lambda URL that takes more than 30 seconds

lambdaUrlTimeout

// This dummy function is just to answer the following simple question:
// Do these new AWS Lambda Function URLs still suffer the same timeout issues that the API Gateway does? Namely 30s?

// Answer: According to my local testing I found they dont suffer the 30s limitation, which is pretty amazing.

exports.handler = async (event) => {
    console.log(event)
    let timeoutSeconds = +event.queryStringParameters.timeout
    if (typeof timeoutSeconds !== 'number') {
        timeoutSeconds = 40
    } else {
        // If value is a number...
        // Clamp the timeout to lambda max timeout (max 15 minutes)
        timeoutSeconds = clamp(timeoutSeconds, 0, 900)
    }
    
    console.log('Before timeout!')
    await timeout(timeoutSeconds)
    console.log('After timeout!')
    const response = {
        statusCode: 200,
        body: JSON.stringify(`Hello from Lambda, after a timeout of ${timeoutSeconds} seconds.`),
    };
    return response;
};

const timeout = async (seconds) => {
    return new Promise((done, reject) => {
        setTimeout(function() {
            done()
        }, seconds * 1000);
    })
}

const clamp = (value, min, max) => {
  return Math.min(Math.max(value, min), max);
}