Skip to main content

Custom Proxy for Statsig API

Instead of sending API requests directly to Statsig, you can set up your own environment that proxies requests from your custom domain name to Statsig.

There are many ways to set up custom proxies. We are showing instructions for a few common service providers here.

AWS CloudFront


  • Write access to your DNS settings.
  • Write access on your AWS CloudFront and Lambda console.
  • Access to a SSL certificate for your custom domain.


On your AWS CloudFront console,

  • Click on Create distribution.

  • In the Origin section,

    • Set the Origin Domain to
    • Set the Protocol to HTTPS only.

Origin section

  • In the Default cache behavior section,

    • Set Viewer protocol policy to Redirect HTTP to HTTPS.
    • Set Allowed HTTP methods to GET, HEAD, OPTIONS, PUT, POST, PATCH, DELETE.
    • In the Cache Key and origin requests subsection, allow all headers and parameters to be forwarded to the Origin, and allow CORS requests for the Origin.

Default cache behavior section

Function associations section

You can use the following javascript code snippet in your Lambda@Edge function:

exports.handler = (event, context, callback) => {
const request = event.Records[0].cf.request;[0].value = '';
return callback(null, request);
  • In Settings,

    • Add an Alternate domain name (CNAME) to be your preferred domain name to use for the custom proxy, e.g.
    • Add a Custom SSL certificate. You will need to follow the AWS guide for Alternate domain name to add a SSL certificate.
    • Click on Create distribution.


  • You will get a Distribution domain name (e.g. once it is provisioned.

In your DNS settings (depending on your DNS provider),

  • Add a CNAME record in your custom DNS record:

    • Host name:
    • Type: CNAME
    • Data: (The Distribution domain name from AWS)

Update Statsig SDK to use your custom domain

When using Statsig SDK, make sure to update the api parameter in the Statsig Options to your custom domain with /v1/ appended, e.g.