Export metadata
Download deployment, audit, configuration identity, and resource records as JSON. Secret values are excluded.
Project configuration
Production activeAcme Store · acme-inc/store
General
Repository and source identity recorded in every deployment snapshot.
The Colonize dashboard is the configuration source.
No repository configuration file is read. Each deployment records the exact dashboard configuration snapshot it used.
Build commands
AWS CodeBuild runs these commands from a clean, no-cache checkout of the exact recorded SHA.
CodeBuild jobSource, scoped build secrets, logs, artifact write
Deployment processValidates the artifact, then mutates AWS
Runtime roleApplication permissions only
Environment variables
Production and Preview values are independent. A Preview never falls back to Production.
Secrets stay write-only.
Secret values never appear in snapshots, audit output, downloads, exports, or untrusted-Preview confirmations.
| Name | Environment | Value | Published | Actions |
|---|---|---|---|---|
| APP_ENV | Production | production | Yes | |
| DATABASE_URL | Production | •••••••••••• | Yes | |
| MAPS_API_KEY | Production | •••••••••••• | Yes | |
| APP_ENV | Preview | preview | Yes | |
| PREVIEW_DATABASE_URL | Preview | •••••••••••• | Yes | |
| MAPS_API_KEY | Preview | •••••••••••• | No |
Custom domain
The active hostname routes Production only. Preview custom domains are not supported.
https://store.example.com
Certificate issued · API mapping active · DNS managed by you
- Certificate
- Colonize-created ACM certificate
- Routing
- Production root mapping
- DNS record
- User-managed · never deleted by Colonize
Object Store
Publish browser assets or downloads from a dedicated S3 bucket.
Enable object store
Turning this off stops using the configuration but does not delete the existing bucket or objects.
Remove Object Store
Permanently delete every object and version, then remove the Colonize-created bucket.
GitHub
Source access, pull-request discovery, checks, and deployment status.
- Installation
- acme-inc
- Repository
- acme-inc/store
- Last sync
- 8 minutes ago
Disconnecting does not stop or remove anything already running.
Colonize marks the project disconnected and disables future source builds until access returns.
Operational data
Colonize retains deployment and audit metadata until you explicitly purge it.
Log bodies remain in AWS
Colonize views or downloads CloudWatch and CodeBuild logs without retaining another long-lived copy.
Delete project resources
Remove Colonize-managed AWS resources while preserving application-owned dependencies and retained metadata.
Production runtime and routeLambda, versions, alias, API route, execution role
Custom domainMapping and unshared Colonize-created certificate only
Object Store42 objects and 6 noncurrent versions
Application dependenciesDatabases, storage, and external services are not removed