Cursor Enterprise: Private Connectivity

Cursor supports private connectivity for Enterprise teams whose Git provider is not reachable from the public internet. The same setup is reused across Cursor services that need source control access, including Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. Press Enter for the full definition., BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition. and Cursor backend services. Two options are supported today.

I used to frame this choice by cloud provider: an AWS shop takes PrivateLinkAn AWS feature that keeps traffic to a service on your private network instead of the public internet. Press Enter for the full definition., everyone else takes the tunnel. That puts the second question first. Start with the directions you need, because the middle column is where the two options stop being interchangeable. PrivateLink is the row that mentions webhook traffic coming back to Cursor; the Cloudflare row covers Cursor reaching a private origin and stops there. If your GitHub Enterprise Server has to send webhooks without public egress, the documented return path runs over PrivateLink.

Both paths assume your Git provider is already serving HTTPS on port 443 with a publicly trusted certificate, and that you control the DNS for its hostname. The rest depends on which path you pick: AWS PrivateLinkAn AWS feature that keeps traffic to a service on your private network instead of the public internet. Press Enter for the full definition. needs AWS permissions to publish endpoint services, while Cloudflare Tunnel only needs permission to run cloudflared, which is the shorter conversation to have with a platform team. Have these in place before you contact Cursor.

• A Cursor Enterprise workspace.
• A self-hosted GitHub Enterprise Server or GitLab Enterprise instance reachable over HTTPS on port 443.
• A publicly trusted TLS certificate for the Git hostname, plus DNS ownership for that hostname.
• AWS permissions to create endpoint services or interface VPC endpoints, if using AWS PrivateLinkAn AWS feature that keeps traffic to a service on your private network instead of the public internet. Press Enter for the full definition..
• Permission to run cloudflared, if using Cloudflare Tunnel.

The certificate is the line that stops projects. Publicly trusted rules out an internal CA, and swapping the certificate on a host your whole engineering org clones from is rarely a same-week job. Check it before you book time with Cursor.

How much of this lands on one person depends on the org. With eight people the AWS account, the GHES box and the DNS zone often have the same owner, so the list is one checklist. In a larger org, three queues. Start the certificate request first.

AWS PrivateLinkAn AWS feature that keeps traffic to a service on your private network instead of the public internet. Press Enter for the full definition. supports private traffic in either direction between Cursor and your Git provider. You may need one direction or both, depending on your network policy, and which ones you need is worth settling before the first call.

For the Cursor-to-Git direction, you publish your provider behind an AWS endpoint service and hand Cursor the details it needs to create its side of the connection. The steps below cover that handoff, and the order in them is load-bearing. Cursor cannot create its interface endpoint until the principal it gives you sits in your allowed-principals list, so leaving that step until last means Cursor's endpoint creation fails with InvalidServiceName, an error that names the service while the cause is in the principal list.

1. 1Create a Network Load Balancer in front of your Git provider's HTTPS endpoint and publish it as an AWS VPC endpoint service.
2. 2Send Cursor the endpoint service name, AWS region, Git hostname, whether AWS-managed private DNS is enabled and whether the load balancer preserves client IPs or your backend filters source IPs.
3. 3Add the exact AWS principal Cursor provides to your endpoint service allowed principals; if it is missing or does not match, AWS returns InvalidServiceName.
4. 4Accept the endpoint connection in your AWS account if your endpoint service requires manual acceptance.
5. 5Configure DNS so the Git hostname matches the TLS certificate and resolves to the endpoint.

For the return direction, Cursor publishes an AWS PrivateLinkAn AWS feature that keeps traffic to a service on your private network instead of the public internet. Press Enter for the full definition. endpoint service for api2.cursor.sh. You create an interface VPC endpoint in your AWS account and enable private DNS so api2.cursor.sh resolves to private endpoint IPs from your Git provider network. Cursor confirms your AWS principal is allowlisted before you create the endpoint, so send the principal, the VPC and region you plan to use, and which DNS mode you want.

AWS-managed private DNS (private_dns_enabled = true) is the recommended mode, since AWS associates your VPC with the managed hosted zone and no Route 53 record is needed. A customer-managed private hosted zone is there if you would rather own the record.

These are the values you plug into that interface endpoint. The service lives in us-east-1 and is IPv4 only, so the supported consumer regions below are what I would check before designing anything around this path.

Use Cloudflare Tunnel when AWS PrivateLinkAn AWS feature that keeps traffic to a service on your private network instead of the public internet. Press Enter for the full definition. is not a fit. Cursor creates the tunnel and shares a public hostname under Cursor-controlled DNS, a tunnel token through a secure 1Password share and a sample cloudflared configuration. Your network runs cloudflared and opens outbound connections to Cloudflare, so no inbound firewall rule is required.

ingress:
  - hostname: <cursor-provided-hostname>
    service: https://<your-internal-service>:443
  - service: http_status:404

The outbound-only shape is probably why this option clears review where PrivateLinkAn AWS feature that keeps traffic to a service on your private network instead of the public internet. Press Enter for the full definition. stalls. Nothing has to open inbound: cloudflared dials out to Cloudflare from inside your network, so the change lands in an egress rule rather than a perimeter exception. What you take on instead is a public hostname under Cursor-controlled DNS in front of an internal service, which is worth putting in front of your security reviewer before the tunnel is built.

After private networking is configured, complete the source control setup in Cursor using the GitHub or GitLab integration steps, and use the same hostname covered by your TLS certificate and private DNS. If your Git provider sends webhooks to Cursor through the api2.cursor.sh PrivateLinkAn AWS feature that keeps traffic to a service on your private network instead of the public internet. Press Enter for the full definition. path, verify resolution and reachability from the same network path the Git provider uses.

A bastion or your own laptop will not tell you much here. The resolver that counts is the one GitHub Enterprise Server or GitLab Enterprise resolves through, and on an older network that is often not the endpoint VPC resolver. Forward api2.cursor.sh queries to the VPC resolver when the provider's DNS sits outside that VPC, and do not create a public override.

getent hosts api2.cursor.sh
# or, if dig is available
dig +short api2.cursor.sh
curl -sS https://api2.cursor.sh/

• Every resolved IP should be inside your consumer VPC CIDR. Public IPs such as 3.x.x.x or 44.x.x.x mean private DNS is not in effect.
• The curl request should return HTTP 200 with a body that starts with Welcome to Cursor., which means the request reached a live Cursor api2 backend.
• If api2.cursor.sh resolves to public IPs, enable AWS-managed private DNS or forward DNS to the endpoint VPC resolver.