AWS edge integration doc #3573

araf-statsig · 2025-09-29T06:38:25Z

Description

Brief summary or screenshot of your changes

Best practice checklist

I've considered the best practices on where to put your doc and what to put in your doc
I've deleted and redirected old pages to this one, if any
I've updated links affected by this change, if any
I've updated screenshots affected by this change, if any

Questions?

Reach out to Brock or Tore on Slack!

jasonwzm · 2025-09-29T06:41:46Z

🚀 Deployed on https://68dae7e5e4b50cbf4eb2153e--cozy-fox-0defec.netlify.app

tore-statsig · 2025-09-29T16:16:03Z

docs/integrations/aws.md

+
+## Overview
+
+Statsig now offers support to use statsig configs on AWS edge services, providing low latency for gate and experiment evaluations in your AWS project.


remove this - "now" is meaningless.

tore-statsig · 2025-09-29T16:16:20Z

docs/integrations/aws.md

+
+Statsig now offers support to use statsig configs on AWS edge services, providing low latency for gate and experiment evaluations in your AWS project.
+
+This integration uses the bring your own CDN model from the statsig edge client. This guide will highlight the most optimal setup for using statsig with AWS to leverage performance on the edge.


"bring your own CDN model from the statsig edge client"

This is also meaningless to someone reading the doc for the first time

removed. I put this sentence here so it made a bit more sense later why the method is called initalizeFromCDN()

tore-statsig · 2025-09-29T16:18:40Z

docs/integrations/aws.md

+
+## S3 Storage Setup
+
+The S3 bucket will be leveraged to store your statsig Config specifications. Since Amazon does not provide a traditional KV store for lambda@edge, we will treat the S3 storage as our KV store.


dont use passive voice. "will be leveraged"

"For edge integrations, the statsig SDK needs access to storage located as close to the lambda as possible. On aws, we recommend storing your statsig project definition in an s3 bucket" or something like that.

Also, can you make this generic? Im pretty sure you can sub gcp function / gcp data store in for lambda/s3

changed section paragraph

This doc walks users through a start to finish setup using AWS. There are many AWS specific components in the doc. Wouldn't it make more sense to have a separate doc for GCP?

tore-statsig · 2025-09-29T16:19:04Z

docs/integrations/aws.md

+- Call the statsig CDN endpoint with you client key.
+
+  ```bash
+  https://api.statsigcdn.com/v1/download_config_specs/<YOUR_CLIENT_API_KEY>.json


make this a curl?

tore-statsig · 2025-09-29T16:19:28Z

docs/integrations/aws.md

+**CRITICAL**: Must be created in **us-east-1** region
+
+1. Change region to **us-east-1** (top-right corner)


why? does this not work otherwise?

https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-how-it-works-tutorial.html#lambda-edge-how-it-works-tutorial-create-function

tore-statsig · 2025-09-29T16:20:01Z

docs/integrations/aws.md

+This setup guide aims to complete every step through the AWS console. We suggest you work on your project on your local. Once you are ready to deploy your code, upload it as a zip to your function's code tab. Ensure your project is built and all packages are installed before you test or deploy it in the Lambda console.
+
+Further explanation and breakdown of the usage of the statsig SDK within this code will be provided later in this guide.


make it clear which variables they need to plug in

tore-statsig · 2025-09-29T16:20:13Z

docs/integrations/aws.md

+Further explanation and breakdown of the usage of the statsig SDK within this code will be provided later in this guide.
+
+```javascript
+import { StatsigEdgeClient } from "@statsig/edge-client";


this doesnt exist yet, but good ot have the docs ready

tore-statsig · 2025-09-29T16:20:38Z

docs/integrations/aws.md

+    callback(null, {
+      status: "200",
+      statusDescription: "OK",
+      headers: {
+        "content-type": [{ key: "Content-Type", value: "application/json" }],
+      },
+      body: JSON.stringify({
+        success: false,
+        error: error.message,
+        message: "Fallback response",
+      }),
+    });


sdk initialization shouldnt really have a fialure case

tore-statsig · 2025-09-29T16:21:03Z

docs/integrations/aws.md

+4. Click **Publish**
+5. **Copy the Version ARN** (ends with :1) - you'll need this for CloudFront
+
+### Create IAM Execution Role for Lambda@Edge


So is this specific to lambda at edge, but not lambda? can we make the setup for just lambda clear?

tore-statsig · 2025-09-29T16:21:27Z

docs/integrations/aws.md

+### Install
+
+```bash
+npm install @statsig/edge-client
+```
+
+Install the statsig edge SDK. This SDK is a one stop shop for all edge integrations, including AWS.


weird that you go back to lambda and THEN break down the code

tore-statsig

This guide doesnt mention anything about how to keep the spec up to date

AWS edge integration doc 1st draft

e8899ee

jasonwzm temporarily deployed to pull request September 29, 2025 06:41 Inactive

spelling fixes

8afcee7

jasonwzm temporarily deployed to pull request September 29, 2025 06:47 Inactive

AWS edge integration doc 2nd draft

dbee0eb

jasonwzm temporarily deployed to pull request September 29, 2025 07:01 Inactive

AWS edge integration doc 3rd draft

95e4dcf

jasonwzm temporarily deployed to pull request September 29, 2025 07:07 Inactive

AWS edge integration doc 4th draft

91f97bd

jasonwzm temporarily deployed to pull request September 29, 2025 07:29 Inactive

Bolding fix

324f5ad

araf-statsig changed the title ~~AWS edge integration doc 1st draft~~ AWS edge integration doc Sep 29, 2025

jasonwzm temporarily deployed to pull request September 29, 2025 07:41 Inactive

spelling mistake

d302bac

jasonwzm temporarily deployed to pull request September 29, 2025 07:49 Inactive

tore-statsig reviewed Sep 29, 2025

View reviewed changes

araf-statsig added 2 commits September 29, 2025 11:42

Address PR review

6dfb900

SpellCheck fix

1bac370

jasonwzm temporarily deployed to pull request September 29, 2025 18:48 Inactive

nits

b787bfd

jasonwzm temporarily deployed to pull request September 29, 2025 19:54 Inactive

spellcheck fix

f6596b5

jasonwzm temporarily deployed to pull request September 29, 2025 20:08 Inactive

capitalize Statsig

5701eda

jasonwzm temporarily deployed to pull request September 29, 2025 20:12 Inactive


		## Overview

		Statsig now offers support to use statsig configs on AWS edge services, providing low latency for gate and experiment evaluations in your AWS project.


		Statsig now offers support to use statsig configs on AWS edge services, providing low latency for gate and experiment evaluations in your AWS project.

		This integration uses the bring your own CDN model from the statsig edge client. This guide will highlight the most optimal setup for using statsig with AWS to leverage performance on the edge.


		## S3 Storage Setup

		The S3 bucket will be leveraged to store your statsig Config specifications. Since Amazon does not provide a traditional KV store for lambda@edge, we will treat the S3 storage as our KV store.

		CRITICAL: Must be created in us-east-1 region

		1. Change region to us-east-1 (top-right corner)

		This setup guide aims to complete every step through the AWS console. We suggest you work on your project on your local. Once you are ready to deploy your code, upload it as a zip to your function's code tab. Ensure your project is built and all packages are installed before you test or deploy it in the Lambda console.

		Further explanation and breakdown of the usage of the statsig SDK within this code will be provided later in this guide.

AWS edge integration doc #3573

Are you sure you want to change the base?

AWS edge integration doc #3573

Uh oh!

Conversation

araf-statsig commented Sep 29, 2025

Description

Best practice checklist

Questions?

Uh oh!

jasonwzm commented Sep 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

tore-statsig left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

jasonwzm commented Sep 29, 2025 •

edited

Loading