when using awswrangler.redshift.connect_temp, does redshift cluster need to be publicly accessible?

[yubiao]

I run awswrangler.redshift.connect_temp on a lambda in the same AWS account as the Redshift cluster. When Redshift cluster is not set to public, I get connection timeout error when running connect_temp. If I set cluster to be public, connection is fine.

Does Redshift cluster have to be public in order for connect_temp to work?

The IAM role for my lambda has the following policy:

      PolicyDocument:
        Version: "2012-10-17"
        Statement:
          - Effect: Allow
            Action:
              - 'redshift:GetClusterCredentials'
              - 'redshift:CreateClusterUser'
              - 'redshift:DescribeClusters'
            Resource:
              - !Sub 'arn:aws:redshift:${AWS::Region}:${AWS::AccountId}:cluster:${RedshiftClusterIdentifier}'
              - !Sub 'arn:aws:redshift:${AWS::Region}:${AWS::AccountId}:dbname:${RedshiftClusterIdentifier}/${RedshiftDatabase}'
              - !Sub 'arn:aws:redshift:${AWS::Region}:${AWS::AccountId}:dbuser:${RedshiftClusterIdentifier}/${DataAppRedshiftUser}'

[yubiao]

updates on this: even I give my lambda the full Redshift permission, arn:aws:iam::aws:policy/AmazonRedshiftFullAccess, it still has the connection timeout error

[ERROR] InterfaceError: ('communication error', TimeoutError(110, 'Connection timed out'))
Traceback (most recent call last):
  File "/var/task/redshift_import_lambda.py", line 12, in handler
    with wr.redshift.connect_temp(
  File "/opt/python/awswrangler/redshift.py", line 582, in connect_temp
    return redshift_connector.connect(
  File "/opt/python/redshift_connector/__init__.py", line 365, in connect
    return Connection(
  File "/opt/python/redshift_connector/core.py", line 619, in __init__
    raise InterfaceError("communication error", e)

[malachi-constant]

Hi @yubiao, is your Lambda Function configured within a VPC with security group ingress to the cluster?

Lambda VPC Configuration