Skip to content

fix: move AWS_SSE_LOGS_BUCKET_NAME to task-processor definition#6284

Merged
gagantrivedi merged 1 commit intomainfrom
fix/sse-logs-bucket-task-processor
Nov 13, 2025
Merged

fix: move AWS_SSE_LOGS_BUCKET_NAME to task-processor definition#6284
gagantrivedi merged 1 commit intomainfrom
fix/sse-logs-bucket-task-processor

Conversation

@gagantrivedi
Copy link
Member

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

PR #6232 re-enabled SSE usage tracking by adding the AWS_SSE_LOGS_BUCKET_NAME environment variable, but it was incorrectly added to the web task definition (ecs-task-definition-web.json) instead of the task processor definition (ecs-task-definition-task-processor.json).

This commit fixes that by:

  • Adding AWS_SSE_LOGS_BUCKET_NAME to ecs-task-definition-task-processor.json
  • Removing AWS_SSE_LOGS_BUCKET_NAME from ecs-task-definition-web.json

The SSE usage tracking logic runs in the task processor, not the api service, so the environment variable needs to be configured in the correct task definition.

How did you test this code?

n/a

PR #6232 re-enabled SSE usage tracking by adding the AWS_SSE_LOGS_BUCKET_NAME
environment variable, but it was incorrectly added to the web task definition
(ecs-task-definition-web.json) instead of the task processor definition
(ecs-task-definition-task-processor.json).

This commit fixes that by:
- Adding AWS_SSE_LOGS_BUCKET_NAME to ecs-task-definition-task-processor.json
- Removing AWS_SSE_LOGS_BUCKET_NAME from ecs-task-definition-web.json

The SSE usage tracking logic runs in the task processor, not the web service,
so the environment variable needs to be configured in the correct task definition.
@gagantrivedi gagantrivedi requested a review from a team as a code owner November 13, 2025 05:20
@gagantrivedi gagantrivedi requested review from khvn26 and removed request for a team November 13, 2025 05:20
@vercel
Copy link

vercel bot commented Nov 13, 2025

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

3 Skipped Deployments
Project Deployment Preview Comments Updated (UTC)
docs Ignored Ignored Nov 13, 2025 5:20am
flagsmith-frontend-preview Ignored Ignored Nov 13, 2025 5:20am
flagsmith-frontend-staging Ignored Ignored Nov 13, 2025 5:20am

@gagantrivedi gagantrivedi requested review from a team and emyller and removed request for a team and khvn26 November 13, 2025 05:24
@gagantrivedi gagantrivedi merged commit 58e0e79 into main Nov 13, 2025
12 checks passed
@gagantrivedi gagantrivedi deleted the fix/sse-logs-bucket-task-processor branch November 13, 2025 07:42
gagantrivedi added a commit that referenced this pull request Nov 13, 2025
Removing AWS_SSE_LOGS_BUCKET_NAME from the task processor for now.
The data processing doesn't seem fast enough yet, so we need to
investigate and optimize before enabling this again.

This temporarily reverts the change from PR #6284.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants