AWSMid

Lambda logs missing from CloudWatch

No logs usually means the execution role lacks CloudWatch permissions. Add AWSLambdaBasicExecutionRole, and know that heavy logging can be throttled or dropped.

What you see

  • The function runs but its log group is empty or missing
  • Some log lines are missing

What it means

A function writes logs through its execution role. Without permission to call CloudWatch Logs, nothing is written. Even with permission, logs can arrive late, be throttled by CloudWatch quotas, or be dropped when output is too fast.

How to confirm the cause

  1. 1
    Check the execution role's policies
    aws iam list-attached-role-policies --role-name ROLE_NAME

    Look for AWSLambdaBasicExecutionRole, and AWSXRayDaemonWriteAccess if you use tracing.

  2. 2
    Check for CloudWatch Logs throttling
    # Service Quotas console: CloudWatch Logs, PutLogEvents / CreateLogStream / CreateLogGroup throttle limits

    Check your utilization against each of those quotas.

Causes and fixes

  • The execution role lacks permission

    HOW TO TELL
    No AWSLambdaBasicExecutionRole on the role.
    ROOT CAUSE
    The function cannot call CloudWatch Logs, so it has nowhere to write.
    FIX
    Attach AWSLambdaBasicExecutionRole. After adding permissions, make a trivial update to the function's code or configuration, so running instances with outdated credentials are replaced.
  • Just not there yet

    HOW TO TELL
    The function ran a moment ago.
    ROOT CAUSE
    Logs can take 5 to 10 minutes to show up after an invocation.
    FIX
    Wait, then look again.
  • Throttled or dropped logging

    HOW TO TELL
    Some lines are missing and the function logs a lot.
    ROOT CAUSE
    If the account reaches CloudWatch Logs quotas, logging is throttled. Lambda also drops logs when output exceeds what it can send; the docs say to expect that consistently above 2 MB/s for one log stream.
    FIX
    Log less, or request a quota increase. Use JSON-formatted logs to get a logsDropped event when drops happen.

How to stop it coming back

  • Attach the basic execution role in your IaC template for every function.
  • Log at a sensible level and sample noisy messages.

Keep going

Sources

AWS documentation (docs.aws.amazon.com), read 18 Nov 2026.

Search

Search cheat sheets and projects