SAM Doctor

ERROR REFERENCE

The CDK assembly builder reported a failure

AssemblyError: Assembly builder failed only says that CDK synthesis stopped. It does not name the app error, dependency, or validation rule. Re-run synthesis with the same project context before changing the generated CloudFormation template.

WHAT IT MEANS

What this message means

[BackendBuildError] Caused by: [_AssemblyError] Assembly builder failed

This is a low-confidence handoff, not a root-cause diagnosis. The CDK Toolkit is reporting a failed cloud-assembly build; the useful exception is usually earlier in the log or is exposed by a verbose synthesis run.

NEXT CHECK

Recover the underlying error

  1. Re-run synthesis with the same inputs:
    cdk synth --verbose
    Use the same project directory, app command, context values, credentials, and environment variables as the failed deployment.
  2. Find the first preceding exception or error. Preserve its complete message and check the app dependencies and CDK context before editing the generated template.
  3. If synthesis succeeds, inspect the deployment event instead. A later CloudFormation resource failure has a more specific status reason than this assembly wrapper.

AUTOMATE THE TRIAGE

Keep the handoff in your normal workflow

SAM Doctor recognizes this wrapper with low confidence and points at a reproducible synthesis check. It does not invent the missing app error. Runs locally; no AWS access, no log upload.

python -m pip install sam-doctor
sam-doctor diagnose deployment.log --format markdown

RELATED