Gathering detailed insights and metrics for serverless-plugin-log-subscription
Gathering detailed insights and metrics for serverless-plugin-log-subscription
Gathering detailed insights and metrics for serverless-plugin-log-subscription
Gathering detailed insights and metrics for serverless-plugin-log-subscription
serverless-plugin-log-subscription-legacy
Attach a CloudWatch LogSubscription to your functions' logs
@keboola/serverless-papertrail-logging
Serverless plugin for log delivery from CloudWatch Logs to Papertrail using a lambda function with log groups subscription
@mikestaub/serverless-papertrail-logging
Serverless plugin for log delivery from CloudWatch Logs to Papertrail using a lambda function with log groups subscription
@eduardocalazansjr/serverless-plugin-log-subscription
Attach a CloudWatch LogSubscription to your functions' logs
npm install serverless-plugin-log-subscription
Typescript
Module System
Node Version
NPM Version
90.5
Supply Chain
97.1
Quality
75.9
Maintenance
100
Vulnerability
98.8
License
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
NOASSERTION License
42 Stars
88 Commits
22 Forks
3 Watchers
22 Branches
16 Contributors
Updated on Jun 10, 2025
Latest Version
3.0.0
Package Id
serverless-plugin-log-subscription@3.0.0
Unpacked Size
17.25 kB
Size
5.12 kB
File Count
5
NPM Version
10.8.2
Node Version
20.18.2
Published on
Feb 24, 2025
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
1
6
This plugin adds an AWS::Logs::LogSubscription
for each of your Lambda functions when enabled.
Log subscriptions are used to deliver your CloudWatch Logs to a destination of some kind. This may be a CloudWatch Destination resource (which wraps a Kinesis stream) or a Lambda function.
As of 2.0, this plugin will automatically create the AWS::Lambda::Permission
if your destinationArn is a reference to a Lambda function within your service.
If you do not want permissions to be created automatically, you can set addLambdaPermission: false
.
The addSourceLambdaPermission option has been removed and will throw an error.
Configuration happens both 'globally' (via custom.logSubscription) and also at the function level (via function.yourFunction.logSubscription)
enabled
- whether or not log subscriptions are enabled. defaults to false globally, if set to true it will be on for all functions (unless they set to false)
destinationArn
(required) - the arn of the CloudWatch Destination (you create this resource yourself) or an Fn::GetAtt reference to a local Lambda function for direct subscription
roleArn
(optional) - the arn of the IAM role granting logs permission to put to Destination (you create this resource yourself)
filterPattern
(optional) if specified, it will only forward logs matching this pattern. You can do simple token matching, or JSON matching (e.g. { $.level >= 30 }
to match a bunyan level)
filterName
(optional) if specified, this name will be used for the FilterName property of the AWS Subscription Filter.
apiGatewayLogs
(optional) if true
the plugin will configure a subscription filter for the API Gateway access and execution log groups. This feature only works if logging is enabled for the API gateway as well.
The most basic:
1custom: 2 logSubscription: 3 destinationArn: 'some-arn' 4 roleArn: 'some-arn' 5 6functions: 7 myFunction: 8 logSubscription: true
Custom function settings:
1custom: 2 logSubscription: 3 destinationArn: 'some-arn' 4 filterName: 'some-filter-name' 5 6functions: 7 myFunction: 8 logSubscription: 9 filterPattern: 'WARN*'
Enabled for all functions:
1custom: 2 logSubscription: 3 enabled: true 4 destinationArn: 'some-arn' 5 roleArn: 'some-arn' 6 7functions: 8 myFunction: 9 ...
Disabled for one function:
1custom: 2 logSubscription: 3 enabled: true 4 destinationArn: 'some-arn' 5 6functions: 7 myFunction: 8 ... 9 myOtherFunction: 10 logSubscription: false
Lambda function directly:
1custom: 2 logSubscription: 3 enabled: true 4 destinationArn: 5 # Note that you have to use Serverless' naming convention here 6 Fn::GetAtt: ['LogsProcessorLambdaFunction', 'Arn'] 7 addLambdaPermission: true # this is the default, set to false to manage your own permissions 8 9functions: 10 api: 11 ... 12 logsProcessor: 13 logSubscription: false # Don't subscribe the log processors logs to the log processor..
Several subscription filters for one log group / the same log group:
Note: Please make sure your AWS account is allowed to use this feature!
By default, AWS allows to use 1 subscription filter per log group and this quota can't be changed.
But, there is an opportunity to ask AWS Support to help you with using several subscription filters for
one log group.
1custom: 2 logSubscription: 3 - enabled: true 4 destinationArn: 'some-arn-1' 5 roleArn: 'some-arn' 6 - enabled: true 7 destinationArn: 'some-arn-2' 8 roleArn: 'some-arn' 9 10functions: 11 myFunction: 12 ...
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
Found 6/21 approved changesets -- score normalized to 2
Reason
dependency not pinned by hash detected -- score normalized to 2
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
40 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More