fix(slack): bump command processor memory to 512 MB#233
Merged
Conversation
Closes aws-samples#231. The command processor was running at the CDK default of 128 MB and OOMing during module init. Symptom: @bgagent mentions in Slack got the 👀 reaction (receiver acked the event) but never the follow-up acknowledgement — the processor crashed before doing anything. CloudWatch logs: INIT_REPORT ... Phase: init Status: error Error Type: Runtime.OutOfMemory REPORT ... Memory Size: 128 MB Max Memory Used: 127 MB Cause: createTaskCore's transitive dependency graph (Cedar engine, attachment-screening, related deps) grew past the 128 MB module-init ceiling. The Slack processor imports createTaskCore so it loads the whole graph even on hot paths that never use attachments. The Linear webhook processor hit the same pattern earlier and was bumped in d843540. Slack's processor was never explicitly sized so it stayed at the default until the bundle finally crossed 128 MB. Followup aws-samples#232 tracks the deeper fix (lazy-load attachment/Cedar deps in createTaskCore so processors don't need 512 MB).
krokoko
approved these changes
Jun 1, 2026
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
2 participants
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.
Summary
Closes #231.
The Slack
CommandProcessorFnruns at the CDK default of 128 MB and OOMs during module init aftercreateTaskCore's transitive dependency graph (Cedar, attachment-screening, etc.) crossed the ceiling. Bump to 512 MB to match the Linear webhook processor (already at 512 from #d843540).Symptom:
@bgagentmentions in Slack get the 👀 reaction (receiver acks the event) but never the follow-up acknowledgement — the processor crashes before doing anything. CloudWatch shows:#232 tracks the deeper followup (lazy-load attachment / Cedar deps in
createTaskCoreso processors don't need 512 MB).Test plan
aws lambda get-function-configurationreturnsMemorySize: 512,@Shoofmentions complete end-to-end (👀 → task created → acknowledgement comment posted)