CLI command to connect to the logs of a running sandbox

[frederikbendel]

Environment information

System:
  OS: Windows 11 10.0.26220
  CPU: (16) x64 AMD Ryzen 7 5700U with Radeon Graphics
  Memory: 44.34 GB / 63.38 GB
Binaries:
  Node: 22.13.0 - C:\Program Files\nodejs\node.EXE
  Yarn: undefined - undefined
  npm: 11.4.2 - C:\Program Files\nodejs\npm.CMD
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/auth-construct: 1.9.0
  @aws-amplify/backend: 1.18.0
  @aws-amplify/backend-ai: Not Found
  @aws-amplify/backend-auth: 1.8.0
  @aws-amplify/backend-cli: 1.8.0
  @aws-amplify/backend-data: 1.6.2
  @aws-amplify/backend-deployer: 2.1.4
  @aws-amplify/backend-function: 1.15.1
  @aws-amplify/backend-output-storage: 1.3.2
  @aws-amplify/backend-secret: 1.4.1
  @aws-amplify/backend-storage: 1.4.2
  @aws-amplify/cli-core: 2.2.2
  @aws-amplify/client-config: 1.9.0
  @aws-amplify/data-construct: 1.16.3
  @aws-amplify/data-schema: 1.22.0
  @aws-amplify/deployed-backend-client: 1.8.1
  @aws-amplify/form-generator: 1.2.5
  @aws-amplify/model-generator: 1.2.1
  @aws-amplify/platform-core: 1.10.2
  @aws-amplify/plugin-types: 1.11.1
  @aws-amplify/sandbox: 2.1.3
  @aws-amplify/schema-generator: 1.4.1
  @aws-cdk/toolkit-lib: 1.6.1
  aws-amplify: 6.15.8
  aws-cdk-lib: 2.223.0
  typescript: 5.9.3
No AWS environment variables
No CDK environment variables

Describe the feature

Another command to stream the logs of a running sandbox.

npx ampx sandbox --stream-function-logs needs to run type checks and a full deployment before.

Use case

I have a big Schema with a deployment time of ~20 mins right now, so when im booting up i can spare that time of deployment.

[pahud]

Hi @frederikbendel,

This appears to be a valid feature request for decoupling log streaming from the deployment cycle in sandbox environments.

Currently, the --stream-function-logs flag is tightly coupled to the sandbox.start() method, which means log streaming only begins after synthesis, type checking, and deployment complete. For large schemas with 20+ minute deployment times, this creates a significant delay when you simply want to view logs from an already-running sandbox.

The underlying LambdaFunctionLogStreamer component is already designed to stream logs independently - it just needs to be exposed through a standalone CLI command.

A potential solution would be adding a new command like npx ampx sandbox logs (or npx ampx logs) that:

• Resolves the sandbox identifier (similar to how sandbox delete works)
• Directly invokes the log streamer without triggering deployment
• Supports the same filtering options (--logs-filter, --logs-out-file)

Making this a p2 FR. Please help us prioritize with 👍