Skip to content

fix(slack): bump command processor memory to 512 MB #233

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
krokoko merged 1 commit into from
Jun 1, 2026
Merged

fix(slack): bump command processor memory to 512 MB #233

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions cdk/src/constructs/slack-integration.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -238,12 +238,17 @@ export class SlackIntegration extends Construct {
}));

// --- Slash Command Processor (async worker) ---
// Memory bumped from default 128 MB → 512 MB after module-init OOM
// surfaced in dev. Bundle grew past the 128 MB cap once createTaskCore's
// transitive dependency graph (Cedar, attachment-screening) imported
// here through the shared task-creation path.
const commandProcessorFn = new lambda.NodejsFunction(this, 'CommandProcessorFn', {
entry: path.join(handlersDir, 'slack-command-processor.ts'),
handler: 'handler',
runtime: Runtime.NODEJS_24_X,
architecture: Architecture.ARM_64,
timeout: Duration.seconds(30),
memorySize: 512,
environment: {
...createTaskEnv,
SLACK_USER_MAPPING_TABLE_NAME: this.userMappingTable.tableName,
Expand Down
Loading