Glue SSL trusted CA

AWS Glue does not provide a specific list of default trusted Certificate Authorities (CAs) for on-premises database connections. However, Glue offers flexibility in handling SSL connections to on-premises databases.

By default, if no custom certificate is specified, AWS Glue will use its default certificate for SSL connections. However, if you need to use a specific certificate for your on-premises database, you have the option to provide a custom certificate.

To use a custom certificate, you can specify it in the Glue connection properties. There are two ways to do this:

1. Custom JDBC certificate in S3: You can upload your custom root certificate to an Amazon S3 location and provide that location in the connection properties. AWS Glue will use this certificate to establish an SSL connection to the database. The certificate must be DER-encoded and supplied in base64 encoding PEM format.

2. Custom JDBC certificate string: You can provide a custom JDBC certificate string directly in the connection properties. This string is used for domain matching or distinguished name matching to prevent man-in-the-middle attacks.

It's important to note that AWS Glue only handles X.509 certificates. If you're using a custom certificate, ensure it meets this requirement.

If you're having trouble connecting to your on-premises database using SSL, you may need to check your network configuration, including DNS resolution and security group settings, to ensure proper connectivity between AWS Glue and your on-premises environment.
Sources
AWS Glue connection properties - AWS Glue
Connection - AWS Glue
Connection API - AWS Glue
Cannot connect to Oracle on-prem from Glue | AWS re:Post