fix: re-enable sse usage tracking

[gagantrivedi]

Thanks for submitting a PR! Please check the boxes below:

• I have added information to docs/ if required so people know about the feature!
• I have filled in the "Changes" section below?
• I have filled in the "How did you test this code" section below?
• I have used a Conventional Commit title for this Pull Request

Changes

Add AWS_SSE_LOGS_BUCKET_NAME environment variable to re-enable SSE usage tracking.
Was disabled here
For more details, ref: #6224

How did you test this code?

n/a

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Ignored	Preview		Nov 3, 2025 11:51am
flagsmith-frontend-preview	Ignored	Preview		Nov 3, 2025 11:51am
flagsmith-frontend-staging	Ignored	Preview		Nov 3, 2025 11:51am

[matthewelwell]

@gagantrivedi can you also add information into the description here to provide context on why we disabled it, and why we're re-enabling it? Please link to any issues, discussions or other relevant PRs.

[gagantrivedi]

@gagantrivedi can you also add information into the description here to provide context on why we disabled it, and why we're re-enabling it? Please link to any issues, discussions or other relevant PRs.

Done

[matthewelwell]

@gagantrivedi I assume then, that these have been done?

• Move existing SSE usage data to a new bucket
• Clean up the current bucket

[axolo-co]

gagantrivedi commented:
We’ll handle this after the release is deployed; otherwise, Fastly will continue pushing data into the bucket, and it will keep accumulating since we’re not processing it.

[matthewelwell]

Then the issue needs updating with the correct steps in the correct order.