cd .. / projects
<deployflow/>

DeployFlow

PLANNED
CI/CD & DevOps Engineering•2026•DevOps Engineer•Planned Project
DeployFlow primary preview
<about-project/>

DeployFlow is the second planned Cloud/DevOps learning build: an automated CI/CD delivery pipeline that ships containerized applications to cloud infrastructure. The intended design uses GitHub Actions for CI/CD, builds and pushes images to AWS ECR, and rolls them out to ECS, with Terraform managing the deployment infrastructure and OIDC replacing long-lived cloud credentials with short-lived identity federation. Bash and Python scripts handle build, test, and release steps, with health gates gating promotion and documented rollback strategies if a release misbehaves. As a DevSecOps-minded pipeline, secrets are injected at deploy time and never baked into images. This extends InfraForge by automating delivery of what the infrastructure runs. This is a planned roadmap build: no pipeline, Docker image, or cloud deployment exists yet.

<tech-stack/>
<key-features/>
GitHub Actions workflow for build, test, and deploy (planned)
Container image builds pushed to AWS ECR (planned)
Deployment to ECS on the InfraForge infrastructure (planned)
OIDC-based cloud access without long-lived keys (planned)
Health gates between environment promotions (planned)
Documented rollback and redeploy strategy (planned)
Secrets injected at deploy time (planned)
<technical-decisions/>

Why OIDC instead of access keys? (planned)

Federating GitHub Actions with AWS through OIDC keeps cloud credentials short-lived and scoped, which is the security-minded approach this pipeline is meant to practice.

Why health gates before promotion? (planned)

Requiring the deployed application to pass health checks before promotion is the intended safety mechanism for catching broken releases before they reach the next environment.