perform-release

Automate production releases by triggering a deployment workflow post-merge, monitoring the ECS rollout, and validating live service health. This coordinates CI prerequisites, ECS task definitions, and health checks to ensure a stable deployment.

Monitor an ECS rollout by tracking new task definitions, service stability, and health checks through the deployment process. The orchestration observes the ECS service until it reaches a healthy state, verifying the live service continuously.

Verify service health after a production deploy by validating live health endpoints and checking application logs. The process surfaces a post-release report to confirm the deployment succeeded and the service is stable.

Yes, you can trigger a GitHub Actions deployment workflow for staging verifications or production deploys. The orchestration applies to any post-merge release, ensuring CI green checks and successful builds are met before triggering.

If an ECS deployment fails, the orchestration uses MCP servers to diagnose failures and guide safe rollbacks. It provides post-release diagnostics to help identify the issue and revert the service to a stable state.

Yes, CI checks must pass before triggering a production deployment. The orchestration enforces CI/CD gated releases by ensuring prerequisites like green CI builds are satisfied before initiating the ECS rollout workflow.