Error: DynamoDB local error spawn java ENOENT

spawn java ENOENT means a launcher could not start Java, usually because java is not on that process’s PATH. Node.js can also report ENOENT when the configured working directory does not exist. Check both before troubleshooting DynamoDB itself.

# macOS or Linux, in the same environment as the launcher:
command -v java
java -version
# Windows PowerShell:
# Get-Command java
# java -version

Install a compatible Java runtime and ensure its bin directory is on the launcher’s PATH. DynamoDB Local 2.6.0 and newer require Java 17 or newer. Setting JAVA_HOME alone does not guarantee that spawning the executable name java will find it. Restart an IDE or shell that inherited the old environment.

For a framework plugin, verify its configured working directory and JAR installation. The maintained serverless-dynamodb plugin replaces the older serverless-dynamodb-local workflow; use its documented setup rather than pinning an obsolete version. Running the official Docker image is another option when a host Java installation is undesirable.

See local setup, Node child-process errors, and serverless-dynamodb setup.