- 최신
- 최다 투표
- 가장 많은 댓글
-
As you have mentioned that you are able to access the LDAP server locally, it seems the concerned error is due to some networking issue.
-
If you're using a connection in your AWS Glue job to connect to the LDAP Server, kindly check its networking configuration. Whenever, we attach a connection, Glue launches elastic network interfaces (ENIs) in a VPC/private subnet which provide network connectivity for AWS Glue through your VPC. Each elastic network interface gets a private IP address from the CIDR range of the subnet used in the connection. No public IP addresses are assigned. [+] https://docs.aws.amazon.com/glue/latest/dg/start-connecting.html
So, all the data stores that are accessed by the job must be available from the VPC subnet. The VPC needs to have a Network Address Translation (NAT) gateway inside the VPC to connect with a public host.
You can verify this by configuring an EC2 instance with the same network configuration as your connection. If you are able to telnet from your EC2 instance terminal to the host without issues, then you have confirmed that the host is reachable.
-
If you're not using any connection in your AWS Glue job, then the traffic would flow from the public IPs. So, make sure your host is accepting the traffic from any public IPs.
-
For specific troubleshooting of your job, you can create a case with the AWS Technical Support and provide the concerned job run id.
