Deployments
How deployments work in StrictOps
Deployments
A deployment represents a single release of your application to AWS. Each deployment tracks the full lifecycle from code push to running service.
Deployment Lifecycle
Every deployment progresses through these statuses:
| Status | Description |
|---|---|
QUEUED | Deployment is waiting to start |
RUNNING | Deployment is in progress |
SUCCEEDED | Deployment completed successfully |
FAILED | Deployment encountered an error |
Deployment Steps
Each deployment consists of ordered steps:
- Build - GitHub Actions builds your Docker image
- Push - Image is pushed to Amazon ECR
- Provision - CloudFormation creates/updates infrastructure
- Deploy - ECS service is updated with the new image
- Verify - Health checks confirm the service is running
If any step fails, the deployment stops and reports the error. You can view which step failed and the error message in the deployment details.
Key Fields
| Field | Description |
|---|---|
serviceId | Name of the service being deployed (from strictops.yml) |
environment | Target environment (e.g., production, staging) |
commitSha | Git commit SHA that triggered the deployment |
repoFullName | GitHub repository (e.g., owner/repo) |
stackId | CloudFormation stack ARN |
serviceUrl | URL of the deployed service |
actionsRunUrl | Link to the GitHub Actions run |
Archiving Deployments
Old deployments can be archived to keep the deployment list clean. Archived deployments are hidden by default but can be retrieved by setting includeArchived to true when listing deployments.
Retrying Failed Deployments
When a deployment fails, you can retry it from the console. The retry creates a new deployment with the same configuration.
Rollbacks
To roll back to a previous version, use the rollback endpoint with the target CloudFormation template. This reverts the ECS service to an earlier configuration.
API Reference
See the Deployments API in Swagger for endpoint details.