What processes managed RedShift connections that would explain initializing connections being stuck for 2m when connection count is

Question

Hello, I'm trying to understand how RedShift manages connections.

I understand that RedShift has a connection limit of 500 which we aren't close to hitting, however we've will intermittently see connections be stuck at initializing for nearly 2m before finally resolving. This is on a new Lambda with normal pg to connect.

Where is connection handling processed, does it have a queue? Does Redshift need to do additional work when using temporary credentials over connecting with username/password?

Answer

The leader node manages communications with client programs, refer https://docs.aws.amazon.com/redshift/latest/dg/c_high_level_system_architecture.html

Using temporary credentials involves additional services, namely IAM and STS, and with Federation an IdP (AWS Directory Service, your enterprise user directory, or a web identity provider) is also involved. Refer 
https://docs.aws.amazon.com/redshift/latest/mgmt/generating-iam-credentials-overview.html

What processes managed RedShift connections that would explain initializing connections being stuck for 2m when connection count is < 250.

Contenus pertinents