- Newest
- Most votes
- Most comments
If Glue is connected to a VPC with connectivity to the on-premises database, as described in the blog post, then is DNS resolution for the internal database name configured as described in the "Other considerations for a hybrid setup" section of the blog post? Does the security group attached to Glue's ENI (elastic network interface) and the rules on any potential on-premises firewalls allow access from Glue's ENI to both the database and the DNS servers? Did you have TLS/SSL encryption enabled/enforced for the JDBC connection?
If you happen to have an EC2 instance in the same VPC, could you test if you can connect to the database from there?
If it isn't easy to confirm the DNS setup, perhaps just to narrow down the problem, you could temporarily try configuring the connection with the database's IP address, so that DNS resolution isn't needed. If that helps, then it's most likely a DNS issue and the configuration for it explained in the blog post would be the first item to check.
Relevant content
- asked 4 years ago
- AWS OFFICIALUpdated 2 years ago

@Leo K, thank you for your response! I configured the connection using the database ip address. But I'm still getting the same error. No, I don't have TLS/SSL encryption enabled.
I'm pretty new to AWS and Glue. Do you by chance have a guide on how to test this in EC2? I appreciate your help. Thank you!
If you have an EC2 instance in the same VPC, make sure that the security group(s) attached to it allow outbound traffic towards the Oracle database. By default, all outbound traffic is permitted, so this is probably already okay. Then just log on to the EC2 instance over SSH or RDP and try connecting to the Oracle database's TCP port 1521 with any tool, such as
telnet. If it doesn't work, even with the IP address, then you probably haven't got connectivity to the on-premises network. Is the connectivity arranged in the way explained in the blog post?@Leo K I created an ec2 instance and ran traceroute and sent it to our network team. They adjusted the firewall rules on their end. The connection worked! Thank you!