Skip to navigation

Cloud NAT gateway

Give AWS, Azure, or Google Cloud servers a static outbound IP for the Chainalysis API

This guide is for servers and integrations that call the Chainalysis API from AWS, Microsoft Azure, or Google Cloud. By default, cloud workloads can leave from ephemeral public IPs that change. A NAT gateway with a static public IP gives every workload in a private subnet one fixed outbound address you can register with Chainalysis.

You can register a limited number of individual IP addresses rather than large ranges. Shared egress addresses used by many organizations, such as a security cloud’s default pool or a cloud provider’s ephemeral IPs, cannot be added to your allowlist.

How it works

StageWhat happensWhere it’s configured
1. WorkloadA server, container, or function in a private subnet that calls api.chainalysis.com.Your VPC or VNet.
2. RouteThe subnet’s default route sends internet traffic to the NAT gateway.Route table or Cloud Router.
3. NAT gatewayTraffic is translated to your static public IP.Elastic IP, Azure public IP, or reserved GCP address.
4. ChainalysisThe request arrives from your registered IP and is accepted.Chainalysis allowlist.

Before you begin

To follow this guide, you’ll need:

  • Admin access to the cloud account and network that runs your Chainalysis integration.
  • The workloads that call Chainalysis placed in private subnets (no public IP of their own).
  • Your Chainalysis CSM contact in order to register your IPs.

Note: A NAT gateway changes the source IP for everything in the subnet, not just Chainalysis calls. Use a dedicated subnet for your Chainalysis integration if you want to keep the address list small.

Chainalysis domains to route

Wherever your platform lets you target destinations, use these domains.

DomainWhat it’s used forNotes
*.chainalysis.comAll Chainalysis products, sign-in, and APIs.We recommend routing through this domain. It covers sign-in and every Chainalysis product, including any you add later.
kyt.chainalysis.comThe KYT user interface.This domain is the minimum required to access KYT. If you use this, you must also route api.chainalysis.com.
api.chainalysis.comThe KYT API and other Chainalysis APIs.This domain is the minimum required to access KYT. If you use this, you must also route kyt.chainalysis.com.

Caution: Ensure that you route by domain, not by IP address. Chainalysis IP addresses change, so rules built on them will break.

Configuration steps

1

Configure your network provider

Expand your network provider’s section below and follow the steps within it.

  1. Allocate an Elastic IP in the VPC console (Elastic IPs > Allocate Elastic IP address).
  2. Create a NAT gateway in a public subnet with Connectivity type: Public and attach the Elastic IP.
  3. In the route table for each private subnet that calls Chainalysis, add a route for 0.0.0.0/0 to the NAT gateway.
  4. For high availability, create one NAT gateway per Availability Zone. Each has its own Elastic IP, and all of them must be registered.

Note: Instances with their own public IP in a public subnet use the internet gateway directly and do not go through the NAT gateway.

  1. Create a Standard SKU static public IP address, or a public IP prefix if you need several addresses.
  2. Create a NAT gateway and attach the public IP or prefix on the Outbound IP tab.
  3. On the Subnet tab, associate the NAT gateway with the subnet(s) that call Chainalysis.
    • NAT gateway becomes the outbound path for those subnets, taking precedence over other outbound methods.

Note: A NAT gateway is zonal. If you deploy one per zone, register every public IP.

  1. Reserve one or more static external IP addresses in the same region as your workloads: gcloud compute addresses create chainalysis-nat-1 --region=REGION.
  2. If you don’t already have one, Create a Cloud Router in that VPC network and region.
  3. Create a Cloud NAT gateway on the router with Manual IP allocation, selecting the reserved addresses: gcloud compute routers nats create chainalysis-nat --router=ROUTER --region=REGION --nat-external-ip-pool=chainalysis-nat-1 --nat-all-subnet-ip-ranges.
    • Don’t use automatic IP allocation since Google can add, remove, or replace auto-allocated addresses.

Note: VMs with their own external IP don’t use Cloud NAT. Each region needs its own NAT gateway and addresses.

2

Register your IPs with Chainalysis

Send the following to your Chainalysis CSM or Chainalysis Support, using the IP submission template:

  • Your dedicated egress IP addresses: IPv4 addresses and, if your network uses IPv6, your IPv6 /64 range.
  • Your organization name and, if you have more than one, the Chainalysis account or organization each IP should apply to.
  • Any other fixed addresses that call Chainalysis outside this platform, such as servers or integrations that use the API.
  • Which cloud, region, and environment (for example, production and staging) each address belongs to.

Your allowlist can contain up to 50 IP addresses. If your number of IPs exceeds 50, you can request an exception through your CSM or Chainalysis Support.

The following table details the types of IPs we support.

What we acceptNotes
Public IPv4 addressesIndividual addresses or small CIDR ranges. Every address in a range counts toward your limit of 50, so a /27 (32 addresses) fits but a /24 (256) does not. If your network needs more, your CSM can discuss an exception.
IPv6 rangesSend your network’s /64 range rather than single addresses. Each /64 counts as one entry. Ranges broader than /64 are subject to approval.
Fixed egress onlyThis includes corporate VPNs, proxies, office gateways, dedicated security-cloud IPs, and cloud NAT addresses.

At this time, we do not accept private addresses (10.x, 172.16-31.x, 192.168.x, 100.64.x), home internet connections, shared or commercial VPN services, shared security-cloud egress pools, or broad ISP ranges.

Your CSM will tell you when the allowlist is live. Do not switch traffic over until they have confirmed.

3

Confirm your connection

  1. From a workload in the private subnet, check its public IP (for example, curl -s https://kyt.chainalysis.com/cdn-cgi/trace). It should return your static IP.
  2. Call api.chainalysis.com with a test request and confirm it succeeds.
  3. Repeat from each region, zone and environment you registered.

When you confirm your connection, we recommend resetting your password (if your organization uses SSO, you can skip this). To reset your password, log out and go to app.chainalysis.com. Enter your email address, click Continue, select Reset password, and follow the on-screen instructions.

We also recommend rotating your API key by following the steps on this page.

If you have issues, please contact support@chainalysis.com.

Common issues

  • Likely cause: The API key doesn’t have the right permissions or the API key must be rotated, even though the IP is allowed.
  • How to resolve: Check the API key’s permissions in your Chainalysis account, or create a new key.
    • API keys created before November 2, 2026 no longer work. To replace one, follow the key rotation steps.
  • Likely cause: Those servers have their own public IP, or sit in a subnet without the NAT route.
  • How to resolve: Move them to the private subnet or add the default route to the NAT gateway.
  • Likely cause: The NAT uses an auto-allocated or dynamic address.
  • How to resolve: Use an Elastic IP, Azure static public IP, or a reserved GCP address with manual allocation.
  • Likely cause: NAT port exhaustion on a single IP.
  • How to resolve: Add another static IP to the NAT gateway and register it by contacting your CSM or Chainalysis Support.
  • Likely cause: Its NAT gateway IP was never registered.
  • How to resolve: Send every NAT IP, in every zone and region, to your CSM or Chainalysis Support.

Additional support

We’re here to help. For questions, contact your Chainalysis CSM or Chainalysis Support.