CloudWatch Logs

CloudWatch Logs Overview

CloudWatch Logs lets you structure AWS Lambda work so it stays readable, testable, and easy to scale. Instead of ad-hoc code, you follow a clear pattern that other developers can recognise immediately.

The key is to keep cloudwatch logs focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

export const handler = async (event) => {
  console.log(JSON.stringify({
    level: 'info',
    requestId: event.requestContext?.requestId,
    message: 'order received',
  }));

  return { ok: true };
};

Structured JSON logs are searchable in CloudWatch Logs Insights and pair well with X-Ray traces.

CloudWatch Logs 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 CloudWatch Logs example and grow it only as needed.
• Keep configuration explicit so CloudWatch Logs behaves the same in every environment.
• Name things clearly so teammates understand your CloudWatch Logs at a glance.
• Add tests around CloudWatch Logs early to lock in expected behaviour.

AWS Lambda Cheatsheet

Handy reference for working with cloudwatch logs in AWS Lambda and Node.js.

How CloudWatch Logs Works in AWS Lambda

CloudWatch Logs 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.

Structured JSON logs are searchable in CloudWatch Logs Insights and pair well with X-Ray traces.

• 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 CloudWatch Logs

On real projects, cloudwatch logs 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 cloudwatch logs.
• Leaving cloudwatch logs untested, so regressions slip into production.
• Over-engineering cloudwatch logs before you actually need the extra flexibility.
• Ignoring documentation, which makes cloudwatch logs hard for the next developer to change.

Key Takeaways

• CloudWatch Logs is a core part of working effectively with AWS Lambda.
• Start small and keep cloudwatch logs focused on a single responsibility.
• Apply consistent patterns so cloudwatch logs scales across your project.
• Test and document cloudwatch logs to keep it maintainable over time.