使用AWS Glue Studio通过CData Athena连接器连接Athena表时遇认证参数缺失错误求助

I’ve helped my team debug a nearly identical issue with the CData AWS Glue Connector for Athena, so here are targeted fixes to try based on your error message and setup:

Key Error Breakdown #

First, let’s highlight the critical part of your error that points straight to the root cause:

Py4JJavaError: An error occurred while calling o61.getSource. : java.lang.AssertionError: assertion failed: Glue ETL Marketplace: Either user/password or secretId should be provided for JDBC connector.

This means the connector isn’t receiving valid authentication credentials through your Glue connection configuration—even if you followed the standard setup guide, there are a few easy-to-miss details.

Step-by-Step Fixes #

1. Explicitly Add Authentication Parameters to Your Glue Connection #

CData’s Athena connector requires explicit auth details, even if you’re using IAM roles for Glue. You have two options here:

• Option 1: Use AWS Secrets Manager
  Create a secret in Secrets Manager containing your AWS access key and secret key (format: {"user": "YOUR_ACCESS_KEY", "password": "YOUR_SECRET_KEY"}), then add the secretId property to your Glue connection’s custom parameters, pointing to the ARN or name of this secret.
• Option 2: Directly Input Credentials (for testing)
  In your Glue connection’s custom properties, add two key-value pairs:
  • user: Your AWS access key ID
  • password: Your AWS secret access key
    Note: This is less secure than using Secrets Manager, but useful for quick validation.

2. Verify IAM Role Permissions #

Ensure the IAM role assigned to your Glue job has these critical permissions:

• If using Secrets Manager: secretsmanager:GetSecretValue for the target secret
• Athena permissions: athena:GetQueryExecution, athena:GetQueryResults, athena:StartQueryExecution
• S3 permissions: s3:GetObject, s3:PutObject for your Athena staging bucket and data storage buckets
• Glue Data Catalog permissions: glue:GetConnection, glue:GetTable, glue:Database to access your Athena tables

3. Check Connector Version & JDBC URL Format #

• Make sure you’re using the latest version of the CData Athena Glue Connector—older versions sometimes have auth logic bugs that trigger this error.
• Verify your JDBC URL in the connection is correctly formatted (CData’s standard Athena URL looks like this):

  jdbc:athena:Region=us-east-1;S3StagingDirectory=s3://your-staging-bucket/path/;
  

  Don’t miss required parameters like Region and S3StagingDirectory.

4. Simplify Testing to Rule Out Conflicts #

Create a minimal test job in Glue Studio that only connects to a single Athena table (no joins yet). This will help you confirm if the issue is with the core connection or something specific to your multi-table association setup.

内容的提问来源于stack exchange，提问作者PPSATO