feat: add S3 overflow for large SQS payloads in Fargate#3684
Merged
Conversation
SQS has 1MB message limit. Large metric batches can exceed this.
When payload > 950KB:
- Worker uploads full payload to S3 at tests/{testId}/overflow/
- Sends reference message with _overflowRef field
- Consumer detects ref, fetches from S3, processes normally
Mirrors existing Azure ACI blob overflow pattern.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
SQS has 1MB message limit. Large metric batches can exceed this.
When payload > 950KB we will now store the payload in S3 instead and fetch it from there in the consumer.
Mirrors existing Azure ACI blob overflow pattern (#3662).
Fixes #3683
Pre-merge checklist
This is for use by the Artillery team. Please leave this in if you're contributing to Artillery.