LLM Proxy IP Whitelist

Control access to your LLM APIs with IP-based whitelist restrictions. Allow only trusted IP addresses to access your AI services and block unauthorized requests before they reach your backend.

🔒 IP Filtering 🌐 CIDR Support ⚡ Real-time Block 📊 Access Logs
🔍

Access Control Log

Active
192.168.1.100
2 seconds ago • /v1/chat/completions
Allowed
10.0.0.50
15 seconds ago • /v1/models
Allowed
203.0.113.42
1 minute ago • /v1/chat/completions
Blocked
Current Whitelist (3 entries)
192.168.1.0/24 10.0.0.50 172.16.0.0/16

IP Whitelist Features

Comprehensive access control for your LLM API infrastructure

🛡️

Real-time Filtering

Instant IP validation at the network edge. Block unauthorized requests before they consume any resources.

🌐

CIDR Notation

Support for CIDR blocks to whitelist entire IP ranges efficiently. Define network segments with ease.

📋

Multiple Lists

Create different whitelists for different endpoints, users, or applications with granular control.

🔄

Dynamic Updates

Add or remove IP addresses without restarting your proxy. Changes take effect immediately.

📊

Access Logging

Complete audit trail of all access attempts, both allowed and blocked, for security analysis.

Zero Latency

IP filtering happens at the connection level with no impact on request latency for allowed IPs.

Supported IP Formats

Flexible IP address formats for different use cases

📍

Single IP Address

192.168.1.100 Specific server
203.0.113.50 Office workstation
198.51.100.10 API consumer
📊

IP Range

192.168.1.1-192.168.1.100 Office range
10.0.0.1-10.0.0.255 Private network
🔢

CIDR Notation

192.168.1.0/24 256 addresses
10.0.0.0/8 Entire private class A
172.16.0.0/12 Private network block
🔄

Dynamic DNS

office.example.com Resolved dynamically
api-client.ddns.net Auto-updating IP

Configuration Example

ip_whitelist.yaml YAML Configuration
# IP Whitelist Configuration
ip_whitelist:
  enabled: true
  default_action: "deny"  # Deny all by default
  
  whitelists:
    # Production servers
    - name: "production"
      ips:
        - "192.168.1.0/24"       # Production network
        - "10.0.1.100"           # CI/CD server
      endpoints:
        - "/v1/*"                # All v1 endpoints
    
    # Office network
    - name: "office"
      ips:
        - "203.0.113.0/24"       # Office IP range
      endpoints:
        - "/v1/chat/*"
        - "/v1/models"
    
    # Dynamic DNS
    - name: "dynamic"
      dns_names:
        - "api-client.example.com"
      refresh_interval: 300  # Refresh every 5 minutes
  
  logging:
    log_allowed: true
    log_denied: true
    include_headers: false

Defense in Depth

1

IP Whitelist

First line of defense - block unauthorized IPs at the network edge.

2

Rate Limiting

Control request volume even from whitelisted IPs to prevent abuse.

3

Authentication

Require API keys or OAuth tokens for additional verification.

4

Authorization

Granular permissions for what each authenticated user can access.

Related Resources

LLM Proxy Connection Pooling

Optimized connection pools for whitelisted IP addresses with dedicated resources.

LLM Proxy Model Fallback

Configure fallback policies that respect IP whitelist restrictions.

LLM Proxy Usage Analytics

Detailed analytics including IP-based access patterns and blocked request metrics.

LLM Proxy PII Masking

Combine IP restrictions with PII protection for comprehensive data security.

Secure Your API Access

Implement IP whitelist protection for your LLM APIs in minutes with our comprehensive solution.