AWS.RDS.signer + Connection pooling ?

I am wondering if you have any suggestions for the following situation:

I would like to use AWS.RDS.signer to generate password tokens for use in a connection pool. I have put together something like the following…

const createPool = () => new Promise((resolve, reject) => {
    signer.getAuthToken({
        region: '...',
        hostname: '...',
        port: '...',
        username: '...'
    }, (err, token) => {
        if (err) reject(err)
        const pool = mysql.createPool({
            host: '...',
            port: '...',
            user: '...',
            database: '...',
            password: token,
            ssl: 'Amazon RDS'
            authSwitchHandler: (data, cb) => {
                if (data.pluginName === 'mysql_clear_password') cb(null, Buffer.from(token + '\0'))
            }
        })
        resolve(pool)
    })
})

…and it works great – but only for 15 minutes, and then the AWS token expires. At that point new connections cannot be established in the pool.

Is there any way to update the pool config options after the pool has been created, so I can keep the token fresh? Would you perhaps consider letting a function be passed as the password property, so that it can return a dynamic value at the time a connection is created? Otherwise, it really isn’t practical to use the aws signer with connection pooling, as I understand it.

[awcchungster]

That worked! Thanks. I really appreciate it.

It would be great to have this in documentation.

For my own learning, how does return () => { change the response object? Is this a specific structure in ES6?

[rabbitfufu]

Thanks for the super fast response, and thanks for the extremely helpful advice! That is exactly what I am looking for. Much appreciated.