Skip to main content
Community Hub
TL;DR

Connect Atlan to an SAP ECC application server over AWS PrivateLink, so RFC traffic stays on the AWS network.

Your AI can read this via Docs MCPcurl -fsSL "https://docs.atlan.com/install-docs-mcp" | bashConnect

Set up AWS private network link to SAP ECC

Connect Atlan to an SAP ECC application server over AWS PrivateLink, so RFC traffic stays on the AWS network. The setup runs in five phases. For who owns each phase and how long it takes, see Private network link FAQ.

How Atlan connects to SAP ECC

Before you set up a private link, read How Atlan connects to SAP ECC. It compares the connectivity methods, lists the connection options each supports, and explains how private connectivity works.

Prerequisites​

  • Chosen a private link as your connectivity method. See How Atlan connects to SAP ECC.
  • Your AWS administrator available to complete most of these steps, and your SAP Basis team available to confirm the application server details.
  • Your Atlan tenant hosted on AWS. For an Atlan tenant on Azure, see Set up Azure private network link to SAP ECC.
  • An SAP ECC application server running in, or reachable by IP from, an AWS VPC that you control. A private link connects to an application server, so you crawl with Connection Type set to Application Server. For every method's options, see Supported connection options.
  • Your SAP system number (NN). The connector derives the gateway port 33NN from the system number, so the load balancer must listen on that same port number.
  • Someone who can create load balancers, target groups, and endpoint services in that VPC.
  • From Atlan, through a support request: your tenant's AWS region, Atlan's AWS account ID, and Atlan's private CIDR range.
Ports in this guide

This guide uses 33NN, where NN is your SAP system number. For system number 00, that's port 3300.

Phase 1: Publish application server​

Owner: Your cloud/network team

Create security groups​

  1. Open the Amazon VPC console and, under Security, click Security Groups.
  2. Create a security group for the NLB in the application server's VPC. Add an outbound rule for Custom TCP, port 33NN, with the application server's security group or IP as the destination.
  3. On the application server's security group, add an inbound rule for Custom TCP, port 33NN, with the NLB security group as the source.
Enforce inbound rules on PrivateLink traffic

NLB security groups enforce inbound rules on PrivateLink traffic by default. Either add an inbound rule to the NLB security group for TCP 33NN from Atlan's private CIDR range, or turn the setting off after you create the load balancer. See Update security settings.

Create target group​

  1. Open the Amazon EC2 console and, under Load Balancing, click Target Groups.
  2. Click Create target group and set:
    • Target type: Instances if the application server runs on EC2 in this VPC, or IP addresses if you register it by IP.
    • Protocol: TCP, Port: 33NN.
    • VPC: The application server's VPC.
    • Health checks: Protocol TCP.
  3. Register the application server as a target on port 33NN, then click Create target group.

Create network load balancer​

  1. Under Load Balancing, click Load Balancers, then Create load balancer and choose Network Load Balancer.
  2. Set Scheme to Internal and IP address type to IPv4.
  3. Under Network mapping, select the VPC and the availability zones with private subnets.
  4. Under Security groups, select the NLB security group.
  5. Add a listener with protocol TCP, port 33NN, forwarding to your target group.
  6. Click Create load balancer.
  7. Open the target group and confirm the application server shows Healthy.
Availability zones must align

Atlan's endpoint and your NLB must share at least one availability zone, or you must turn on cross-zone load balancing on the NLB. Otherwise connections time out even though everything shows healthy and approved.

Create endpoint service​

  1. In the VPC console, under Virtual private cloud, click Endpoint services, then Create endpoint service.
  2. Set Load balancer type to Network and select your NLB.
  3. Turn on Acceptance required. Leave Enable private DNS name cleared. Set Supported IP address types to IPv4.
  4. Click Create.
  5. From the endpoint service Details tab, copy the Service name and the Availability Zones.
  6. On the Allow principals tab, click Allow principals and add Atlan's account as arn:aws:iam::<atlan-account-id>:root.

Phase 2: Share details with Atlan​

Owner: You

Raise a support request and include everything in one message:

  • Your Atlan tenant URL.
  • That the link is for SAP ECC.
  • The endpoint service name and its availability zones.
  • The AWS region of the endpoint service.
  • The gateway port, 33NN.
  • The role on your side that accepts the endpoint connection.

Phase 3: Atlan builds its endpoint​

Owner: Atlan support

Atlan creates an interface VPC endpoint in your tenant's network that targets your endpoint service. This usually takes one to two business days. Atlan support tells you when the endpoint connection is waiting for your acceptance.

Phase 4: Approve connection​

Owner: Your cloud/network team

  1. In the VPC console, open Endpoint services and select your endpoint service.
  2. On the Endpoint connections tab, select the connection in the Pending acceptance state.
  3. Click Actions > Accept endpoint connection request.
  4. Confirm the connection state changes to Available, then reply on your support request.

Atlan support then sends you the endpoint hostname to use in the crawler.

Phase 5: Connect and verify​

Owner: You, in Atlan

When you crawl SAP ECC, choose the Direct extraction method and set:

  • SAP Host Name: The endpoint hostname from Atlan support. Don't use the endpoint service name or the application server's own hostname.
  • Connection Type: Application Server.
  • SAP System Number: Your SAP system number. The connector derives port 33NN from it.

Then click Test Authentication.

Success checklist​

  • The endpoint connection shows Available under Endpoint connections.
  • The target group shows the application server as Healthy.
  • Test Authentication passes in Atlan.
  • Preflight checks pass.
  • A crawl scoped to one small component completes.
  • A full crawl completes.

Troubleshooting​

If the connection fails, see Troubleshooting SAP ECC private network link for each error, its cause, and its solution.

See also​