AWS Glue Connection - Failed to test connection due to FAILED status
0
Hi all,
I've been trying to test a AWS Glue connection to an external MariaDB instance and I'm getting the following error constantly:
I'm unable to understand the root cause of the issue. Not sure if its a SSL certificate or networking issue.
I was successfully able to connect to the external DB through a temporary Amazon EC2 instance, but Glue is unable to connect. I used the same VPCs in both scenarios.
Thanks,
2 Answers
- Newest
- Most votes
- Most comments
0
- I am not able to read out your snap shot. I guess it is from CloudWatch.
- Check out CloudWatch to see the error message it pushes out.
- I would check for IAM issue first.
answered 8 months ago
0
I have the same error in Lake Formation. I observed all the checks for IAM Role, VPC, Security Group, NAT Gateway, but it does not connect to the base via JBDC. Did anyone solve the problem?
answered 5 months ago
Relevant content
AWS OFFICIALUpdated 3 years ago- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
The CloudWatch error message is as follows:
'Check that your connection definition references your JDBC database with correct URL syntax, username, and password. Check that your VPC/subnet has network access to AWS S3 and the connection definition contains a security group with an outbound port rule which can access S3.'
The IAM role that I'm using has 2 amazon-managed permission policies attached to it: AWSGlueServiceRole & IAMFullAccess