Event Source Filtering

Event Source Filtering Overview

Event Source Filtering is a building block you will reach for often in AWS Lambda. It keeps related logic together and makes your intent obvious to reviewers and future maintainers.

When you learn event source filtering properly, you avoid the guesswork that leads to bugs and rework. The example below shows the shape you will use in most real AWS Lambda projects.

export const handler = async (event) => {
  for (const record of event.Records ?? []) {
    const body = JSON.parse(record.body);
    console.log('processing message', body.id);
    // handle each message idempotently
  }

  return { batchItemFailures: [] };
};

Iterating over event.Records lets one Lambda process a batch of messages from SQS, SNS, or streams.

Event Source Filtering Example

// handler.mjs
export const handler = async (event, context) => {
  // 1. read input from the event
  // 2. do the work
  // 3. return a response (or throw on error)
};

• Start from a minimal Event Source Filtering example and grow it only as needed.
• Keep configuration explicit so Event Source Filtering behaves the same in every environment.
• Name things clearly so teammates understand your Event Source Filtering at a glance.
• Add tests around Event Source Filtering early to lock in expected behaviour.

AWS Lambda Cheatsheet

Handy reference for working with event source filtering in AWS Lambda and Node.js.

How Event Source Filtering Works in AWS Lambda

Event Source Filtering runs inside the managed Lambda execution environment. AWS provisions a micro-VM, loads your Node.js code, runs any module-scope initialisation once, and then invokes your handler for each event.

Iterating over event.Records lets one Lambda process a batch of messages from SQS, SNS, or streams.

• Handlers should be small and do one job well.
• Initialise SDK clients and config outside the handler to reuse them on warm starts.
• Return quickly and let event sources handle retries where possible.
• Emit structured logs so CloudWatch and X-Ray can correlate activity.

Practical Guidance for Event Source Filtering

On real projects, event source filtering works best when it is observable, secure, and cheap to run. Grant least-privilege IAM, validate every input, and keep the deployment package small.

Common Mistakes

• Skipping error handling and edge cases when wiring up event source filtering.
• Leaving event source filtering untested, so regressions slip into production.
• Over-engineering event source filtering before you actually need the extra flexibility.
• Ignoring documentation, which makes event source filtering hard for the next developer to change.

Key Takeaways

• Event Source Filtering is a core part of working effectively with AWS Lambda.
• Start small and keep event source filtering focused on a single responsibility.
• Apply consistent patterns so event source filtering scales across your project.
• Test and document event source filtering to keep it maintainable over time.