How do I troubleshoot errors with an AWS Glue connection that has a JDBC source?

Short description

To connect to a JDBC data source, an AWS Glue connection must be configured with parameters that match the data source's details.

The following issues can stop AWS Glue from connecting to a JDBC data source:

• JDBC's URL isn't configured correctly.
• AWS Glue doesn't have a necessary AWS Identity and Access Management (IAM) permission.
• There's a networking issue.
• Your database credentials or database object permissions are incorrect.

Resolution

To troubleshoot these issues, use the AWSSupport-TroubleshootGlueConnection runbook in Automation, a capability of AWS Systems Manager.

Prerequisite: Before you start the AWSSupport-TroubleshootGlueConnection runbook, make sure that your IAM user or role has the required permissions. For more information, see the Required IAM permissions section of AWSSupport-TroubleshootGlueConnection.

Complete the following steps:

1. Open the AWSSupport-TroubleshootGlueConnection document on the Systems Manager console.
2. Choose Execute automation.
3. Enter the following values for the input parameters:
   AutomationAssumeRole (Optional): The ARN of the IAM role that allows Automation to run. If you don't specify a role, then Automation uses the permissions of the user that starts the runbook.
   TestConnectionRole (Required): The ARN of the IAM role that the connection test uses.
   ConnectionName (Required): The name of the failed AWS Glue connection that you must troubleshoot.
   PersistReachabilityAnalyzerResults (Optional): This parameter determines if Automation stores Reachability Analyzer's results. This parameter's default value is false.
   PointOfPresenceLogRetentionPeriod (Optional): The length of time that Automation stores the AWS Lambda logs that the runbook creates. This parameter's default value is 7 days.
   DatasourceSubnets (Optional): If the original data source is not available, then use this parameter to provide the subnets that it uses. You must use this parameter with DatasourceSecurityGroups.
   DatasourceSecurityGroups (Optional): If the original data source is not available, use this parameter to provide the security groups that it uses. You must use this parameter with DatasourceSubnets.
4. Choose Execute.
   Note: For more information about the checks that the runbook performs, see step 6 of the Instructions section of AWSSupport-TroubleshootGlueConnection.
5. Review the detailed results in the runbook's Outputs, and then complete any actions listed in the Automation Results section.
   Note: For more information about the runbook's output, see step 7 of the Instructions section of AWSSupport-TroubleshootGlueConnection.
6. Verify that your database credentials are configured correctly.