Setting the file. One moment.
Skill 50 · Connecting To Data Source
Subchapter 50.4
references/jdbc-setup.mdMarkdown3 KBView on GitHub
AWS Glue JDBC connections for Oracle, SQL Server, PostgreSQL, MySQL, MariaDB, Amazon RDS, Amazon Aurora, and Amazon Redshift.
| Engine | JDBC URL template | Driver class |
|---|---|---|
| Oracle | jdbc:oracle:thin:@//<host>:<port>/<service> | oracle.jdbc.OracleDriver |
| SQL Server | jdbc:sqlserver://<host>:<port>;databaseName=<db> | com.microsoft.sqlserver.jdbc.SQLServerDriver |
| PostgreSQL | jdbc:postgresql://<host>:<port>/<db> | org.postgresql.Driver |
| MySQL / MariaDB | jdbc:mysql://<host>:<port>/<db> | com.mysql.cj.jdbc.Driver |
| Redshift | jdbc:redshift://<cluster>.<region>.redshift.amazonaws.com:5439/<db> | com.amazon.redshift.jdbc.Driver |
For Oracle, prefer the service name form (@//host:port/service). SID form (@host:port:SID) works but is deprecated in Oracle 12c+.
Glue includes drivers for Oracle, SQL Server, PostgreSQL, MySQL, and Redshift. No JDBC_DRIVER_JAR_URI needed.
For driver versions not built into Glue, upload the JAR to S3 and reference:
aws s3 cp ojdbc8-21.jar s3://<scripts-bucket>/jdbc-drivers/Add to connection properties:
"JDBC_DRIVER_JAR_URI": "s3://<scripts-bucket>/jdbc-drivers/ojdbc8-21.jar",
"JDBC_DRIVER_CLASS_NAME": "oracle.jdbc.OracleDriver"{
"Name": "<connection-name>",
"ConnectionType": "JDBC",
"ConnectionProperties": {
"JDBC_CONNECTION_URL": "<url>",
"SECRET_ID": "<secrets-manager-arn-or-name>",
"JDBC_ENFORCE_SSL": "true"
},
"PhysicalConnectionRequirements": {
"SubnetId": "subnet-xxxxx",
"SecurityGroupIdList": ["sg-xxxxx"],
"AvailabilityZone": "<region>-<az>"
}
}The secret should contain username and password keys. Omit USERNAME/PASSWORD from properties when using SECRET_ID.
Redshift accepts both JDBC password auth and IAM-based GetClusterCredentials.
Password-based: use the JDBC template above.
IAM-based (preferred for human/role users): search AWS docs for "Redshift GetClusterCredentials Glue". The Glue role needs redshift:GetClusterCredentials on the cluster; no Secrets Manager secret.
For Redshift Serverless, use the workgroup endpoint and redshift-serverless:GetCredentials.
<instance-id>.<hash>.<region>.rds.amazonaws.com<cluster-id>.cluster-<hash>.<region>.rds.amazonaws.com<cluster-id>.cluster-ro-<hash>.<region>.rds.amazonaws.com – prefer for ETL readsIAM database authentication (Aurora MySQL, Aurora PostgreSQL, RDS MySQL, RDS PostgreSQL):
--enable-iam-database-authenticationCREATE USER etl_user IDENTIFIED WITH AWSAuthenticationPlugin AS 'RDS'rds-db:connect at runtime to get a 15-minute tokenPrefer IAM auth over password auth where supported.