2 Answers
- Newest
- Most votes
- Most comments
1
If you have already configured VPC for glue to access it should not through timeout error, But timeout could suggest that security group on redshift is not configure to accept the request.
Here are a few troubleshooting steps you can try:
- Check the security group rules to allow inbound/outbound traffic between Glue and Redshift.
- You can try connecting to the Redshift cluster using a SQL client or running a simple query to verify its availability by launching an instance in same subnet you are using for glue.
- Increase connection timeout: You can try increasing the connection timeout value in your Glue job's connection options. Add the connectTimeout parameter to the rds_conn_options dictionary with a higher value, such as connectTimeout=120000 (milliseconds).
Example:
rds_conn_options = {
"database": "your_database",
"dbtable": "your_table",
"user": "your_username",
"password": "your_password",
"url": "your_redshift_url",
"connectTimeout": 120000
}
answered a year ago
1
Hey Nitin
Thank you for the guidance. As suggested I did try reading from the redshift, I dont have any issues with it and Im able to fetch the data. Im still facing the same connectivity issue(increased the timeout period) while writing the data. Attaching the vpc screenshot for reference:
answered a year ago
Relevant content
- asked 6 years ago
- AWS OFFICIALUpdated a month ago