Glue Connection (Version 2) for redshift

The issue you're experiencing with the Glue Connection (Version 2) for Redshift seems to be related to network connectivity or permissions, despite having similar settings to the working Version 1 connection. Here's a step-by-step troubleshooting guide to help resolve the "Request timed out validating credentials" error:

1. VPC Endpoints: Ensure you have the necessary VPC endpoints set up correctly. In addition to the S3 gateway endpoint and AWS Secrets Manager interface endpoint you mentioned, also create VPC endpoints for:

   • AWS KMS (interface type)
   • Redshift (interface type)
   • Security Token Service (STS) (interface type) Make sure all these endpoints have private DNS enabled.

2. IAM Permissions: Verify that the IAM role associated with your Glue job has the required permissions. It should include:

   • S3 access
   • GlueServiceRole permissions
   • SecretsManager access
   • KMS permissions
   • Redshift permissions (including DescribeClusters and, for Redshift Serverless, ListWorkgroups and ListNamespaces)

3. Security Groups: Review the security group settings to ensure they allow necessary traffic. The security group should permit:

   • Inbound traffic from Glue to Redshift (typically on port 5439)
   • Outbound traffic to S3, Secrets Manager, KMS, and STS

4. Network ACLs: Check if there are any Network ACLs in place that might be blocking traffic between Glue and the required services.

5. Redshift Cluster Configuration: If using a provisioned Redshift cluster, verify its accessibility settings. For Redshift Serverless, ensure the workgroup and namespace settings are correct.

6. Credentials: Double-check that the credentials stored in Secrets Manager for Redshift access are correct and up-to-date.

7. Connection Details: Verify that the connection details (endpoint, port, database name) in the Glue connection configuration are accurate.

8. VPC Peering (if applicable): If your Redshift cluster is in a different VPC, ensure proper VPC peering and routing is set up.

9. CloudTrail Logs: Review AWS CloudTrail logs for any permission-related issues that might not be immediately apparent.

10. Glue Studio: Try creating the connection using AWS Glue Studio, which might provide more detailed error messages or a guided setup process.

11. AWS CLI: As a workaround, you could try using the AWS CLI to create a custom connector for Redshift with the JDBC URL.

If after following these steps the issue persists, it may be worth contacting AWS Support for further assistance, as there could be specific Version 2 connection intricacies or potential bugs that aren't publicly documented.

Remember that while Version 1 and Version 2 connections might seem similar, there could be underlying differences in how they handle networking or authentication, which might explain why one works while the other doesn't despite similar configurations.
Sources
The new version 2 redshift connection for Glue fails | AWS re:Post
while testing redshift connection from glue i am getting below error | AWS re:Post
Fail to deliver data from RDS to Redshift through AWS Glue | AWS re:Post