@beesolve/lambda-keep-active 1.2.0 → 1.3.0

package/.jsii

@@ -8,8 +8,8 @@
     ]
   },
   "dependencies": {
-    "aws-cdk-lib": "^2.231.0",
-    "constructs": "^10.4.3"
+    "aws-cdk-lib": "^2.235.1",
+    "constructs": "^10.4.5"
   },
   "dependencyClosure": {
     "@aws-cdk/asset-awscli-v1": {
@@ -642,6 +642,19 @@
             }
           }
         },
+        "aws-cdk-lib.aws_cases": {
+          "targets": {
+            "dotnet": {
+              "namespace": "Amazon.CDK.AWS.Cases"
+            },
+            "java": {
+              "package": "software.amazon.awscdk.services.cases"
+            },
+            "python": {
+              "module": "aws_cdk.aws_cases"
+            }
+          }
+        },
         "aws-cdk-lib.aws_cassandra": {
           "targets": {
             "dotnet": {
@@ -1202,6 +1215,19 @@
             }
           }
         },
+        "aws-cdk-lib.aws_devopsagent": {
+          "targets": {
+            "dotnet": {
+              "namespace": "Amazon.CDK.AWS.DevOpsAgent"
+            },
+            "java": {
+              "package": "software.amazon.awscdk.services.devopsagent"
+            },
+            "python": {
+              "module": "aws_cdk.aws_devopsagent"
+            }
+          }
+        },
         "aws-cdk-lib.aws_devopsguru": {
           "targets": {
             "dotnet": {
@@ -4593,6 +4619,22 @@
             }
           }
         },
+        "aws-cdk-lib.interfaces.aws_cases": {
+          "targets": {
+            "dotnet": {
+              "namespace": "Amazon.CDK.Interfaces.Cases"
+            },
+            "go": {
+              "packageName": "interfacesawscases"
+            },
+            "java": {
+              "package": "software.amazon.awscdk.interfaces.cases"
+            },
+            "python": {
+              "module": "aws_cdk.interfaces.aws_cases"
+            }
+          }
+        },
         "aws-cdk-lib.interfaces.aws_cassandra": {
           "targets": {
             "dotnet": {
@@ -5217,6 +5259,22 @@
             }
           }
         },
+        "aws-cdk-lib.interfaces.aws_devopsagent": {
+          "targets": {
+            "dotnet": {
+              "namespace": "Amazon.CDK.Interfaces.DevOpsAgent"
+            },
+            "go": {
+              "packageName": "interfacesawsdevopsagent"
+            },
+            "java": {
+              "package": "software.amazon.awscdk.interfaces.devopsagent"
+            },
+            "python": {
+              "module": "aws_cdk.interfaces.aws_devopsagent"
+            }
+          }
+        },
         "aws-cdk-lib.interfaces.aws_devopsguru": {
           "targets": {
             "dotnet": {
@@ -8412,7 +8470,7 @@
     "stability": "stable"
   },
   "homepage": "https://github.com/beesolve/lambda-keep-active",
-  "jsiiVersion": "5.9.14 (build 9fc28bd)",
+  "jsiiVersion": "5.9.23 (build 29252a0)",
   "keywords": [
     "active",
     "aws",
@@ -8430,7 +8488,7 @@
   },
   "name": "@beesolve/lambda-keep-active",
   "readme": {
-    "markdown": "# Lambda Keep Active\n\n[![View on Construct Hub](https://constructs.dev/badge?package=%40beesolve%2Flambda-keep-active)](https://constructs.dev/packages/@beesolve/lambda-keep-active)\n\n> A function becomes inactive when it has been idle long enough for Lambda to reclaim the external resources that were configured for it. When you try to invoke a function that is inactive, the invocation fails and Lambda sets the function to pending state until the function resources are recreated. If Lambda fails to recreate the resources, the function returns to the inactive state. You might need to resolve any errors and redeploy your function to restore it to the active state.\n>\n> [Lambda function states](https://docs.aws.amazon.com/lambda/latest/dg/functions-states.html)\n\nWhenever your Lambda function becames `inactive` waking it up might take up to 90 seconds as per [this article](https://aws.amazon.com/blogs/compute/announcing-improved-vpc-networking-for-aws-lambda-functions/).\n\nIn order to avoid your Lambda functions to transition to `inactive` state you should invoke them periodically.\n\nNo-one really knows what the \"long enough\" actually means but there is [general consenzus](https://stackoverflow.com/questions/77584016/how-long-before-idle-lambda-function-transitions-to-inactive-state/77691745#77691745) that it might be around 14 days.\n\nAt BeeSolve we are invoking our Lambda functions every 3 days in order to be sure they won't transition to `inactive` state.\n\n## Installation\n\nYou can install Lambda Keep Active helper through npm or any other npm compatible package manager:\n\n```bash\nnpm i @beesolve/lambda-keep-active\n```\n\n## Usage\n\n```ts\n// stack.ts\nimport { LambdaKeepActive } from \"@beesolve/lambda-keep-active\";\n\nconst warmer = new LambdaKeepActive(this, \"KeepAliveLambda\");\n\nconst handler = new NodejsFunction(this, 'Handler', { /** your props */});\n\nwarmer.keepActive(handler);\n```\n\nFor Node.js Lambda handlers you can use `keptActive` wrapper like this:\n\n```ts\n// handler.ts\nimport { keptActive } from \"@beesolve/lambda-keep-active\";\n\nexport const handler = keptActive(async () => {\n  // your handler code\n});\n```\n\nFor [Bun Lambda handlers](https://github.com/BeeSolve/lambda-bun-runtime) you can use `keptActiveFetch` wrapper like this:\n\n```ts\n// bunHandler.ts\nimport { keptActiveFetch } from \"@beesolve/lambda-keep-active\";\n\nexport default {\n  fetch: keptActiveFetch(async (request: Request): Promise<Response> => {\n    // your handler code\n    return new Response();\n  }),\n};\n```\n"
+    "markdown": "# Lambda Keep Active\n\n[![View on Construct Hub](https://constructs.dev/badge?package=%40beesolve%2Flambda-keep-active)](https://constructs.dev/packages/@beesolve/lambda-keep-active)\n\n> A function becomes inactive when it has been idle long enough for Lambda to reclaim the external resources that were configured for it. When you try to invoke a function that is inactive, the invocation fails and Lambda sets the function to pending state until the function resources are recreated. If Lambda fails to recreate the resources, the function returns to the inactive state. You might need to resolve any errors and redeploy your function to restore it to the active state.\n>\n> [Lambda function states](https://docs.aws.amazon.com/lambda/latest/dg/functions-states.html)\n\nWhenever your Lambda function becames `inactive` waking it up might take up to 90 seconds as per [this article](https://aws.amazon.com/blogs/compute/announcing-improved-vpc-networking-for-aws-lambda-functions/).\n\nIn order to avoid your Lambda functions to transition to `inactive` state you should invoke them periodically.\n\nNo-one really knows what the \"long enough\" actually means but there is [general consenzus](https://stackoverflow.com/questions/77584016/how-long-before-idle-lambda-function-transitions-to-inactive-state/77691745#77691745) that it might be around 14 days.\n\nAt BeeSolve we are invoking our Lambda functions every 3 days in order to be sure they won't transition to `inactive` state.\n\n## Installation\n\nYou can install Lambda Keep Active helper through npm or any other npm compatible package manager:\n\n```bash\nnpm i @beesolve/lambda-keep-active\n```\n\n## Usage\n\n```ts\n// stack.ts\nimport { LambdaKeepActive } from \"@beesolve/lambda-keep-active\";\n\nconst warmer = new LambdaKeepActive(this, \"KeepAliveLambda\");\n\nconst handler = new NodejsFunction(this, 'Handler', { /** your props */});\n\nwarmer.keepActive(handler);\n```\n\nFor Node.js Lambda handlers you can use `keptActive` wrapper like this:\n\n```ts\n// handler.ts\nimport { keptActive } from \"@beesolve/lambda-keep-active/runtime\";\n\nexport const handler = keptActive(async () => {\n  // your handler code\n});\n```\n\nFor [Bun Lambda handlers](https://github.com/BeeSolve/lambda-bun-runtime) you can use `keptActiveFetch` wrapper like this:\n\n```ts\n// bunHandler.ts\nimport { keptActiveFetch } from \"@beesolve/lambda-keep-active/runtime\";\n\nexport default {\n  fetch: keptActiveFetch(async (request: Request): Promise<Response> => {\n    // your handler code\n    return new Response();\n  }),\n};\n```\n"
   },
   "repository": {
     "type": "git",
@@ -8456,7 +8514,7 @@
         },
         "locationInModule": {
           "filename": "src/cdk.ts",
-          "line": 20
+          "line": 32
         },
         "parameters": [
           {
@@ -8483,7 +8541,7 @@
       "kind": "class",
       "locationInModule": {
         "filename": "src/cdk.ts",
-        "line": 19
+        "line": 31
       },
       "methods": [
         {
@@ -8492,7 +8550,7 @@
           },
           "locationInModule": {
             "filename": "src/cdk.ts",
-            "line": 54
+            "line": 71
           },
           "name": "keepActive",
           "parameters": [
@@ -8518,7 +8576,7 @@
       "kind": "interface",
       "locationInModule": {
         "filename": "src/cdk.ts",
-        "line": 10
+        "line": 11
       },
       "name": "LambdaKeepActiveProps",
       "properties": [
@@ -8532,18 +8590,36 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/cdk.ts",
-            "line": 16
+            "line": 17
           },
           "name": "enableLogs",
           "optional": true,
           "type": {
             "primitive": "boolean"
           }
+        },
+        {
+          "abstract": true,
+          "docs": {
+            "default": "{\n  removalPolicy: RemovalPolicy.DESTROY,\n  retention: RetentionDays.TWO_WEEKS\n}",
+            "stability": "stable",
+            "summary": "Adjusts logging for SQS handler."
+          },
+          "immutable": true,
+          "locationInModule": {
+            "filename": "src/cdk.ts",
+            "line": 28
+          },
+          "name": "logGroupProps",
+          "optional": true,
+          "type": {
+            "fqn": "aws-cdk-lib.aws_logs.LogGroupProps"
+          }
         }
       ],
       "symbolId": "src/cdk:LambdaKeepActiveProps"
     }
   },
-  "version": "1.2.0",
-  "fingerprint": "rAXSXmARg8zRp5HBuL7ToXOkRYu21gJ5+Fc5SqmKVrY="
+  "version": "1.3.0",
+  "fingerprint": "5LjDZ2MO0kpk17Gk/dJStMKkJVCU+RRdJ+7pGM0Bhoc="
 }

package/API.md

@@ -145,6 +145,7 @@ const lambdaKeepActiveProps: LambdaKeepActiveProps = { ... }
 | **Name** | **Type** | **Description** |
 | --- | --- | --- |
 | <code><a href="#@beesolve/lambda-keep-active.LambdaKeepActiveProps.property.enableLogs">enableLogs</a></code> | <code>boolean</code> | If disabled no logs are logged to CloudWatch. |
+| <code><a href="#@beesolve/lambda-keep-active.LambdaKeepActiveProps.property.logGroupProps">logGroupProps</a></code> | <code>aws-cdk-lib.aws_logs.LogGroupProps</code> | Adjusts logging for SQS handler. |
 
 ---
 
@@ -161,5 +162,18 @@ If disabled no logs are logged to CloudWatch.
 
 ---
 
+##### `logGroupProps`<sup>Optional</sup> <a name="logGroupProps" id="@beesolve/lambda-keep-active.LambdaKeepActiveProps.property.logGroupProps"></a>
+
+```typescript
+public readonly logGroupProps: LogGroupProps;
+```
+
+- *Type:* aws-cdk-lib.aws_logs.LogGroupProps
+- *Default:* {   removalPolicy: RemovalPolicy.DESTROY,   retention: RetentionDays.TWO_WEEKS }
+
+Adjusts logging for SQS handler.
+
+---
+
 
 

package/CHANGELOG.md

@@ -1,4 +1,11 @@
 
+## [1.2.0](https://github.com/beesolve/lambda-keep-active/compare/v1.1.2...v1.2.0) (2025-12-16)
+
+
+### Features
+
+* split runtime and cdk constructs ([b212fef](https://github.com/beesolve/lambda-keep-active/commit/b212fef5181c30c356ff679b40cafd17c438ae80))
+
 ## [1.1.2](https://github.com/beesolve/lambda-keep-active/compare/v1.1.1...v1.1.2) (2025-12-04)
 
 ## [1.1.1](https://github.com/beesolve/lambda-keep-active/compare/v1.1.0...v1.1.1) (2025-12-03)
@@ -10,4 +17,3 @@
 
 * change to projen ([2ed9a40](https://github.com/beesolve/lambda-keep-active/commit/2ed9a4040373b7353d4d8b08601151ceb2e8aa07))
 * fix config ([307d174](https://github.com/beesolve/lambda-keep-active/commit/307d1744a51f2f0dd5af18c653fa9cf51df27c6d))
-

package/LICENSE

@@ -1,4 +1,4 @@
-Copyright (c) 2025 BeeSolve s.r.o.
+Copyright (c) 2026 BeeSolve s.r.o.
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package/README.md

@@ -39,7 +39,7 @@ For Node.js Lambda handlers you can use `keptActive` wrapper like this:
 
 ```ts
 // handler.ts
-import { keptActive } from "@beesolve/lambda-keep-active";
+import { keptActive } from "@beesolve/lambda-keep-active/runtime";
 
 export const handler = keptActive(async () => {
   // your handler code
@@ -50,7 +50,7 @@ For [Bun Lambda handlers](https://github.com/BeeSolve/lambda-bun-runtime) you ca
 
 ```ts
 // bunHandler.ts
-import { keptActiveFetch } from "@beesolve/lambda-keep-active";
+import { keptActiveFetch } from "@beesolve/lambda-keep-active/runtime";
 
 export default {
   fetch: keptActiveFetch(async (request: Request): Promise<Response> => {