Troubleshooting SAP S/4HANA private network link
Troubleshoot an AWS or Azure private network link between Atlan and SAP S/4HANA with error, cause, and solution guidance.
Resolve common issues with an AWS or Azure private network link between Atlan and SAP S/4HANA. In this guide, 33NN is the gateway port, where NN is your SAP system number.
AWS endpoint connection stays pending acceptance
Endpoint connection stays in the Pending acceptance state
Cause
Your team hasn't accepted Atlan's endpoint connection yet.
Solution
- In the Amazon VPC console, open Endpoint services and select your endpoint service.
- On the Endpoint connections tab, select the connection in the Pending acceptance state.
- Click Actions > Accept endpoint connection request, and confirm the state changes to Available.
AWS connection times out after acceptance
Connection times out after the endpoint connection is accepted
Cause
The target is unhealthy, Atlan's endpoint and your Network Load Balancer (NLB) share no availability zone, or a security group blocks port 33NN.
Solution
- Open the target group and confirm the application server shows Healthy.
- Confirm the NLB and Atlan's endpoint share at least one availability zone, or turn on cross-zone load balancing on the NLB.
- Check every security group in the path, including the NLB security group, for TCP
33NN.
AWS connection refused on endpoint hostname
Connection refused on the endpoint hostname
Cause
The NLB listener or target group port doesn't match your SAP system number.
Solution
- Set the NLB listener port and the target group port to
33NNfor your system number. - In Atlan, run Test Authentication again.
Azure private endpoint connection stays pending
Private endpoint connection stays in the Pending state
Cause
Your team hasn't approved Atlan's private endpoint connection yet.
Solution
- In the Azure portal, go to Private Link Center > Private link services and open your service.
- Click Private endpoint connections, select the pending connection whose name matches the one from Atlan support, and click Approve.
- Confirm the connection state changes to Approved.
Azure connection times out after approval
Connection times out after the private endpoint connection is approved
Cause
The load balancer health probe is unhealthy, or a network security group or host firewall blocks port 33NN from the Private Link Service NAT subnet.
Solution
- Confirm the load balancer health probe shows the application server as Healthy.
- Check every network security group in the path for an inbound rule that permits TCP
33NNfrom the NAT subnet. - If the application server runs a host firewall, permit TCP
33NNfrom the NAT subnet there too.
Azure connection refused on endpoint hostname
Connection refused on the endpoint hostname
Cause
The load balancing rule port doesn't match your SAP system number.
Solution
- Set the frontend and back-end port of the load balancing rule to
33NNfor your system number. - In Atlan, run Test Authentication again.
See also
- Set up AWS private network link to SAP S/4HANA: Publish your application server over AWS PrivateLink
- Set up Azure private network link to SAP S/4HANA: Publish your application server over Azure Private Link
Need help
If you need assistance after trying the steps, contact Atlan support: Submit a request.