feat: add CloudWatch LogGroup with retention policy to Lambda functions#117
Merged
feat: add CloudWatch LogGroup with retention policy to Lambda functions#117
Conversation
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
pushed a commit
that referenced
this pull request
Mar 22, 2026
🤖 I have created a release *beep* *boop* --- ## [2.1.0](v2.0.0...v2.1.0) (2026-03-22) ### Features * add /update-snapshot comment trigger to update_snapshot workflow ([764a4fa](764a4fa)) * add CloudWatch LogGroup with retention policy to Lambda functions ([#117](#117)) ([53877bb](53877bb)), closes [#103](#103) * **database:** enable Data API and connection logging ([#123](#123)) ([e32dc7a](e32dc7a)) * increase webapp Lambda memory from 512MB to 1024MB ([#116](#116)) ([03c5a00](03c5a00)), closes [#101](#101) ### Bug Fixes * add lambda:InvokeFunction permission for CloudFront OAC ([#83](#83)) ([3cc66bf](3cc66bf)) * **auth:** improve auth error handling and fix Link CORS issue ([#120](#120)) ([84be605](84be605)) * disable Cognito self sign-up by default ([#115](#115)) ([9396e6f](9396e6f)), closes [#106](#106) * prevent CloudFront cache poisoning for Next.js RSC responses ([#119](#119)) ([70cddda](70cddda)) * **prisma:** add retry for Aurora Serverless v2 connection errors ([#121](#121)) ([7c05dfb](7c05dfb)) * support Amazon Linux 2023 for NAT instance ([#81](#81)) ([0c41aa8](0c41aa8)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.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.
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
LogGroupwithRetentionDays.ONE_WEEKandRemovalPolicy.DESTROYto:cdk/lib/constructs/webapp.tscdk/lib/constructs/webapp.tscdk/lib/constructs/async-job.tsCDK 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