OpenClaw 2026.3.31 regression: Control UI returns 500 and logs amazon-bedrock module load errors

[Schnitzel]

Summary

Upgrading to the OpenClaw 2026.3.31 runtime appears to break the Control UI in OpenClaw Lagoon. In our testing, the gateway started but the UI returned 500 Internal Server Error for / and even static asset paths like /favicon.svg.

At the same time, the gateway logs repeatedly emitted this error:

[plugins] amazon-bedrock failed to load from /usr/local/lib/node_modules/openclaw/dist/extensions/amazon-bedrock/index.js: Error: Cannot find module '@aws-sdk/client-bedrock'
Require stack:
- /usr/local/lib/node_modules/openclaw/dist/discovery-Bwev8dJL.js

We do not use Bedrock in this deployment.

Impact

We cannot safely upgrade OpenClaw Lagoon to the build that pulled in OpenClaw 2026.3.31 until this is fixed.

What we observed

• A working environment on OpenClaw 2026.3.28 served the Control UI normally.
• A broken environment on OpenClaw 2026.3.31 returned 500 for / and static UI asset paths.
• The persisted OpenClaw config looked effectively the same between the working and broken environments.
• The key difference was the runtime version, not the deployment config.
• When the runtime moved back to 2026.3.28, the route started returning 200 OK again.

Suspected cause

This looks like a packaging or runtime regression in OpenClaw 2026.3.31:

• amazon-bedrock is bundled as a stock extension in that runtime.
• The runtime tries to load it during plugin or provider discovery.
• The required module @aws-sdk/client-bedrock was missing or not resolved correctly in the image.
• That failure appears to leave the gateway in a bad state where Control UI requests return 500.

Even if the exact failure path is elsewhere, 2026.3.31 clearly introduced a Bedrock-related plugin loading problem that correlates with the broken UI.

Requested fix

We need to fix the 2026.3.31 image or runtime path before this repo can upgrade to the newer OpenClaw version.

At minimum, one of these should be true:

• the bundled Bedrock provider includes its required runtime dependency correctly, or
• unused bundled providers fail in an isolated, non-fatal way and do not break the Control UI.

Temporary mitigation

Pin to a known-good OpenClaw image version instead of latest until the upstream or runtime issue is fixed.