Listen to this Post
Event-driven architectures on AWS often rely on Lambda functions triggered by events from sources like DynamoDB, SQS, or Kinesis. However, you may only want your Lambda function to execute for specific events rather than every event from the source. This is where event filters in Event Source Mapping come into play.
Using the AWS Cloud Development Kit (CDK), you can configure these filters to ensure your Lambda function processes only the relevant events, reducing unnecessary invocations and optimizing costs.
You Should Know:
1. Setting Up Event Filters with AWS CDK
To implement event filtering, you define a filter pattern in your CDK stack. Below is an example using TypeScript:
import as cdk from 'aws-cdk-lib';
import as lambda from 'aws-cdk-lib/aws-lambda';
import as sqs from 'aws-cdk-lib/aws-sqs';
import as lambdaEventSources from 'aws-cdk-lib/aws-lambda-event-sources';
const app = new cdk.App();
const stack = new cdk.Stack(app, 'LambdaFilterStack');
// Create a Lambda function
const myLambda = new lambda.Function(stack, 'MyLambda', {
runtime: lambda.Runtime.NODEJS_18_X,
handler: 'index.handler',
code: lambda.Code.fromAsset('lambda'),
});
// Create an SQS queue
const queue = new sqs.Queue(stack, 'MyQueue');
// Add event source with filter
myLambda.addEventSource(new lambdaEventSources.SqsEventSource(queue, {
filters: [
lambda.FilterCriteria.filter({
body: {
// Only trigger if 'eventType' is 'OrderPlaced'
eventType: ['OrderPlaced'],
},
}),
],
}));
2. Supported Filter Patterns
AWS Lambda supports filtering on:
- SQS: Message body attributes.
- DynamoDB Streams: Modified record keys or values.
- Kinesis: Data records matching specific JSON structures.
Example for DynamoDB Streams:
myLambda.addEventSource(new lambdaEventSources.DynamoEventSource(table, {
filters: [
lambda.FilterCriteria.filter({
eventName: ['INSERT', 'MODIFY'], // Only INSERT or MODIFY events
}),
],
}));
3. Testing Event Filters Locally
Use AWS SAM CLI to test filters before deployment:
sam local invoke MyLambda -e test-event.json
Where `test-event.json` contains a sample event payload.
4. Monitoring Filtered Invocations
Check CloudWatch Logs for filtered-out events:
aws logs filter-log-events --log-group-name "/aws/lambda/MyLambda" --filter-pattern "FilterCriteria"
5. Common Use Cases
- Order Processing: Trigger only for `OrderPlaced` events.
- Fraud Detection: Filter transactions exceeding a threshold.
- Log Analysis: Process only logs with `ERROR` level.
What Undercode Say
Event filtering in AWS Lambda ensures efficient resource usage by reducing unnecessary function executions. By leveraging AWS CDK, you can programmatically define filters, making infrastructure deployment repeatable and scalable.
For further optimization:
- Use Dead Letter Queues (DLQ) for failed events.
- Monitor Lambda Concurrency to avoid throttling.
- Combine with Step Functions for complex workflows.
Expected Output:
A well-structured AWS CDK stack that deploys a Lambda function with event filtering, ensuring only relevant events trigger execution.
Reference: how.wtf (original article link).
References:
Reported By: Darryl Ruggles – Hackers Feeds
Extra Hub: Undercode MoN
Basic Verification: Pass ✅
