Project

Logs

Bodies remain in AWS. Colonize reads or downloads them without retaining a long-lived copy.

UTC+08:00
10:14:02checkoutCloning acme-inc/docs at commit b1076ea
10:14:05checkoutValidated root directory ./ and package-lock.json
10:14:06prepareStarting clean no-cache CodeBuild environment · colonize/node22-arm64:2026.08
10:14:30prepareDependency install complete
10:14:31assemblePreparing declared deployment directory .build/
10:14:49assembleDetected HTTP runtime entrypoint and production dependencies
10:14:50buildBuilding application pages and browser assets
10:15:28buildBuild completed with 18 routes and 42 assets
10:15:29packageAssembling immutable deployment artifact
10:15:45packageArtifact sha256:7b20…c91e · 38.4 MB uncompressed
10:15:46deployPublishing application version 42 in ap-southeast-1
10:16:05deployTrusted deployment role moved production alias to version 42
10:16:06verifyHealth check passed in 642 ms
10:16:08verifyDeployment ready

Source and configuration

The exact dashboard state and source identity used for this deployment.

Repository
acme-inc/store
Root
./
Commit
b1076ea
Configuration snapshot
cfg_2de410
Build contract
node-http-v1
Builder image
colonize/node22-arm64:2026.08
Workspace
Clean checkout · cache disabled

Permission boundary

Building, deploying, and running use separate AWS roles.

CodeBuild roleRead source and inputs · read scoped build secrets · write logs and artifact
Colonize deployment roleValidate recorded artifact · publish Lambda and route changes
Lambda runtime roleApplication runtime permissions only
Production route
production → version 42
Endpoint
https://docs-portal.deploy.example
Runtime logs
/aws/lambda/colonize-acme-store
Metadata retention
Until manual Colonize purge

Production route

Promote deployment?

Production will move to dpl_b1076e after verification.

The immutable artifact will not be rebuilt. External data changes are outside this route change.