AWS Lambda · static outbound IPs

Static outbound IPs for AWS Lambda.

Static IPs dedicated to your account, for the functions that call your partner. Keep your proxy URL in the function’s environment variables, and only those calls leave from your IPs.

From $29/mo · we set up your IPs with you · 7-day money-back guarantee

  • Dedicated to your account
  • HIPAA-ready on every plan
  • by GitView
AWS Lambda

Lambda, Node.js runtime · Example

// index.mjs: a Lambda function on a Node.js runtime// Bundle undici with the function// npm install undiciimport { fetch, ProxyAgent } from "undici"; let agent;const proxy = () => (agent ??= new ProxyAgent(process.env.STATICPEAR_URL)); export const handler = async () => {  const res = await fetch("https://api.partner.example/v1/orders", {    dispatcher: proxy(),  });  return res.json();};
Example. Only calls that use the proxy leave from your IPs. Source: docs.aws.amazon.com/lambda(opens in a new tab) · undici ProxyAgent docs(opens in a new tab) · checked Nov 14, 2026
Pricing from
$29 / month
Runs on
AWS Lambda
Requests
No count limit
Guarantee
7-day money-back

01 · How it works

Four steps to a fixed IP on AWS Lambda.

Keep the proxy URL in the function’s environment variables, and send the functions that call your partner through it.

  1. Step 1: Pick a plan

    Sign up with your email and a card, and agree to the Terms. We set up your IPs with you. 7-day money-back guarantee.

    PlansMonthly
    $29Starter1 pair · 25 GB a month
    $49Pro1 pair · 100 GB a month

    7-day money-back guarantee

  2. Step 2: Approve your hosts

    Your proxy can only reach the hosts you approve. List the exact host names your app calls, such as your partner’s API. Today that means HTTPS on port 443.

    Approved hostsExample
    api.partner.example:443Approved
    Any other hostRefused
    Other ports, IP addressesRefused
  3. Step 3: Set the proxy URL

    Keep it in the function’s environment variables. Then send the functions that call your partner through it.

    AWS Lambda setupExample
    STATICPEAR_URL="<your proxy URL>"

    Kept inthe function’s environment variables

    Used bythe functions that call your partner

  4. Step 4: Allowlist your IPs

    Send your partner your two static IPs. They add both to their allowlist.

    Partner allowlistExample
    203.0.113.24Allowed
    198.51.100.17Allowed
    Everyone elseNot listed

Works from any app whose HTTP client accepts an HTTPS proxy URL (TLS to the proxy).

02 · On AWS Lambda

AWS Lambda setup, in detail.

Where it applies
The functions that call your partner. Other traffic leaves the way it does today.
Runs on
Node.js
Proxy URL
Kept in the function’s environment variables.
Proxy
Works from any app whose HTTP client accepts an HTTPS proxy URL (TLS to the proxy).
Approved hosts
Your proxy can only reach the hosts you approve. Exact host names, HTTPS on port 443. You choose them during setup.
Sources

03 · Dedicated

Dedicated IPs, not shared, from $29.

A shared static IP also carries other customers’ traffic, and an allowlist that trusts the IP trusts all of it. StaticPear IPs are dedicated to your account, on every plan.

7-day money-back guarantee

Shared static IP

For contrast

Sends from these IPs

  • Your app
  • Other customers

The IP your partner allowlists

  • 198.51.100.9

The allowlist lets in every customer on that IP.

StaticPear · dedicated pair

Every plan

Sends from these IPs

  • Your app
  • No one else

The IPs your partner allowlists

  • 203.0.113.24
  • 198.51.100.17

The allowlist lets in your app’s traffic only.

Example addresses

Entry plan, billed monthly
$29/ mo
In every pair
2IPs
Dedicated, on every plan
1pair
On the number of requests
Nolimit

7-day money-back guarantee

04 · Security

Built to be allowlisted.

Approved hosts
Your proxy can only reach the hosts you approve. Exact host names, HTTPS on port 443.
Dedicated
Your IPs carry only your traffic, never another customer’s.
Placement
Two dedicated static IPs on separate servers in separate AWS availability zones.
TLS to the proxy
Your app connects to the proxy over TLS, then the proxy connects to your approved host.
Health data
HIPAA-ready on every plan. BAA available on request. We never store request or response contents.

05 · Pricing

Plans start at $29 a month.

Every plan: dedicated static IPs and no limit on the number of requests. Plans differ only by the data they include. 7-day money-back guarantee.

06 · FAQ

Common questions about AWS Lambda.

Which hosts can my IPs reach?

Your proxy can only reach the hosts you approve. You list the exact host names your app calls. Today that means HTTPS on port 443. Requests to any other host, to an IP address, to private or internal networks, or to mail ports are refused.

Why two IPs?

Two dedicated static IPs on separate servers in separate AWS availability zones. Allowlist both IPs. Each IP has its own proxy endpoint: if a connection through one fails, your app retries through the other.

Do you log my traffic?

Connection metadata only (destination host, bytes, timing), never contents. For each connection the proxy logs the time, the method, the destination host and port, the server IP address it resolved to, the status, bytes in and out, and how long it lasted. Query strings are stripped, and no URL paths, headers or bodies are logged. The Privacy Policy lists every record we keep and for how long.

Can I try it first?

Every plan comes with a 7-day money-back guarantee on your first payment. The Terms have the details.

Questions before you start?

07 · Get started

Get static IPs for AWS Lambda.

Static outbound IPs for the functions that call your partner, from $29 a month. Your partner allowlists them once.

From $29/mo · we set up your IPs with you · 7-day money-back guarantee