Skip to content

feat: add CloudWatch LogGroup with retention policy to Lambda functions#117

Merged
konokenj merged 1 commit intomainfrom
add-loggroup-retention
Mar 20, 2026
Merged

feat: add CloudWatch LogGroup with retention policy to Lambda functions#117
konokenj merged 1 commit intomainfrom
add-loggroup-retention

Conversation

@konokenj
Copy link
Contributor

Summary

Add explicit CDK-managed CloudWatch LogGroups with 1-week retention to all Lambda functions to prevent unbounded log storage costs.

Problem

Without explicit LogGroup configuration, Lambda auto-creates LogGroups with infinite retention. As logs accumulate, storage costs grow without bound.

Changes

Added LogGroup with RetentionDays.ONE_WEEK and RemovalPolicy.DESTROY to:

Construct Lambda File
Webapp Handler cdk/lib/constructs/webapp.ts
Webapp MigrationRunner cdk/lib/constructs/webapp.ts
AsyncJob Handler cdk/lib/constructs/async-job.ts

CDK test snapshots updated accordingly.

Out of scope

Lambda@Edge (SignPayload) is excluded — edge-region LogGroups cannot be managed by CDK and will become unnecessary after #66.

Closes #103

Add explicit CDK-managed LogGroups with 1-week retention to all Lambda
functions (Webapp Handler, MigrationRunner, AsyncJob Handler). Without
this, Lambda auto-creates LogGroups with infinite retention, causing
unbounded log storage costs.

Lambda@Edge (SignPayload) is excluded since edge-region LogGroups cannot
be managed by CDK and will be addressed separately (#66).

Closes #103
@konokenj konokenj added this to the v2-fix milestone Mar 20, 2026
@konokenj konokenj merged commit 53877bb into main Mar 20, 2026
5 checks passed
@konokenj konokenj deleted the add-loggroup-retention branch March 20, 2026 01:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Lambda関数のCloudWatch LogGroupにretention policyを設定する

1 participant