Forum Discussion
Can not connect to amazon redshift database - timeout expired
Details: "ODBC: ERROR [08S01] [Microsoft][Amazon Redshift] (10) Error occurred while trying to connect: [SQLState 08S01] timeout expired
"
Getting this error when trying to connect to the amazon redshift. What does this mean
Hi arsalaan ,
In terms of Redshift, please check:
1) Wrong hostname or port
2) Publicly Accessible is set "NO" in your Redshift cluster configuration (Only VPC)
If you launched your Redshift cluster in VPC, Publicly Accessible: needs to be YES to access from outside VPC.
3) VPC security group is not configured correctly
There are two patterns to setup security groups to access Redshift.
- Non-VCP: Redshift Securiy group settings
- VPC: VPC security group settings
Check if you setup the correct security group settings along with the place where you launched your Redshift cluster.
Besides, in terms of PBI you can check the following settings:
1)Check if the gateway is installed and working properly.
2)Optimize the query or reduce the amount of data to be refreshed.
3)Refresh the data during off-peak hours when the data source is less busyFor more details, please refer to:
Troubleshooting Connection Issues in Amazon Redshift
Best Regards,
Jianbo Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
1 Reply
- v-jianboli-msft
Community Support
Hi arsalaan ,
In terms of Redshift, please check:
1) Wrong hostname or port
2) Publicly Accessible is set "NO" in your Redshift cluster configuration (Only VPC)
If you launched your Redshift cluster in VPC, Publicly Accessible: needs to be YES to access from outside VPC.
3) VPC security group is not configured correctly
There are two patterns to setup security groups to access Redshift.
- Non-VCP: Redshift Securiy group settings
- VPC: VPC security group settings
Check if you setup the correct security group settings along with the place where you launched your Redshift cluster.
Besides, in terms of PBI you can check the following settings:
1)Check if the gateway is installed and working properly.
2)Optimize the query or reduce the amount of data to be refreshed.
3)Refresh the data during off-peak hours when the data source is less busyFor more details, please refer to:
Troubleshooting Connection Issues in Amazon Redshift
Best Regards,
Jianbo Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.