How do I troubleshoot failed AWS Glue connections to external data sources?

Resolution

First, troubleshoot a failed test connection. If AWS Glue still can't connect to your data source, then complete the following resolution for the connector that you use.

OpenSearch connection issues

If you receive a "Cannot detect OpenSearch version" error, then take the following actions:

• In the connection properties for your cloud or Wide Area Network (WAN) environment, set opensearch.nodes.wan.only to true.
• If you use Elasticsearch, then enter the following code to your cluster to activate compatibility mode:

  PUT /_cluster/settings  
  {  
    "persistent": {  
      "compatibility.override_main_response_version": true  
    }  
  }

Kafka connection issues

Kafka accepts only keystores that are in .jks format. If you receive a "Failed to load SSL keystore" error, then verify that your keystore is in .jks format.

MongoDB connection issues

Complete the resolution for the error that you receive.

MongoDB authentication failure

If you receive an "Exception authenticating MongoCredential" error, then verify the following configurations:

• Your username and password match the MongoDB credentials that your application uses.
• Your authentication method specifies the correct authentication database.
• You correctly formatted your MongoDB connection's URL in your authentication mechanism and your authentication source.

For more information, see Connect with Java Database Connectivity (JDBC) Driver on the MongoDB website.

MongoDB or DocumentDB connection errors in AWS Glue 4.0

If you receive the following error when you use AWS Glue 4.0, then verify that you correctly configured the MongoDB connector's properties and URL formats:

"Mongo/DocumentDB connection URL is not supported."

For more information, see Batch read configuration options on the MongoDB website.

Snowflake connection errors

First, verify the following configurations:

• Your AWS Glue job uses a Snowflake connection.
• You configured your Snowflake connection's URL parameters in the order of user, database, role_name, and warehouse.
• Your connection adheres to AWS Glue's Snowflake connector limitations.

Then, complete the resolution for the error that you receive.

Errors with connections that you made with Boto3

If you used Boto3 to create your Snowflake connection, then check that you correctly configured the SparkProperties parameter.

Example configuration with correct property:

{  
     "Connection": {  
         "Name": "Snowflake connection",  
         "Description": "",  
         "ConnectionType": "SNOWFLAKE",  
         "ConnectionProperties": {  
             "SparkProperties": "{\"sfUrl\":\"https://account.snowflakecomputing.com\",\"secretId\":\"mySecret\"}"  
         },  
         "CreationTime": 1708694242.804,  
         "LastUpdatedTime": 1708694242.804,  
         "LastUpdatedBy": "..."  
     }  
 }

HTTP Response code 403

If you receive a "HTTP Response code: 403, request: POST" error, then make sure that your Snowflake connection's URL, username, and password are accurate. Then, verify that you correctly configured your network configuration. For more information about Snowflake role permissions, see Access control considerations on the Snowflake website.

JDBC communication error: connect timeout

If you receive a "JDBC driver encountered communication" error, then verify that your connection setup uses a private subnet. Then, configure a NAT gateway in your AWS Glue connection's subnet that routes traffic to Snowflake.

ConnectTimeoutError with Snowflake Marketplace Connector

If you receive the following error, then set up a NAT gateway in your AWS Glue connection's subnet:

"Connect timeout on endpoint URL."

The NAT gateway must allow access to your Amazon Elastic Container Registry (Amazon ECR) repository.

OCSP certificate revocation error

If you receive a "Driver is connecting to an HTTPS endpoint without OCSP based Certificate Revocation" error, then deactivate Online Certificate Status Protocol (OSCP) checking. For more information, see How To: Turn off OCSP checking in Snowflake client drivers on the Snowflake website.

Teradata Vantage connection issues

Complete the resolution for the error that you receive.

Login timeout for connection

If you receive a "Login timeout for connection" error, then verify that your network setup allows AWS Glue to access the Teradata Vantage host.

Single sign-on not supported for Mechanism TD2

If you receive a "Single sign-on not supported for Mechanism TD2" error, then verify that you correctly configured your network setup. Then, make sure that the connection string contains the correct username and password. Don't use single sign-on credentials.

Vertica connection issues

Verify that your network setup allows AWS Glue to access the Vertica host.