M. ENGINEERING SYSTEMS
PORTFOLIO / 2026
INITIALIZING 00%
M.
A LITTLE SPACE TO BUILD BIG THINGS

WELCOME.

TO MOMNA'S ENGINEERING WORLD

CLOUD✳ DEVOPS✳ AUTOMATION✳ RELIABILITY✳ KUBERNETES✳ CLOUD✳ DEVOPS✳ AUTOMATION✳ RELIABILITY✳ KUBERNETES✳
SYSTEMS WITH PURPOSE
01 — 06
CASE STUDY 01 / DEVOPS ENGINEERING
CI/CD AUTOMATION

From commit
to cloud.

CI/CD Pipeline with Flask, Docker, GitHub Actions, Terraform & AWS EC2

Automating application delivery with GitHub Actions, Docker, Terraform and Amazon EC2.

GITHUB ACTIONS DOCKER TERRAFORM AWS EC2 FLASK
DELIVERY PIPELINE 01 — 05
01
GitHub Push to main
↘
02
GitHub Actions Build workflow
↘
03
Docker Hub Publish image
↘
04
Amazon EC2 SSH deployment
↘
05
Flask Container Application runtime
TARGET
CONTAINER DELIVERY GITHUB → AWS
PROJECT TYPE CI/CD Pipeline
APPLICATION Python / Flask
INFRASTRUCTURE Terraform / EC2
IMAGE REGISTRY Docker Hub
ENGINEERING SPECIFICATIONCI/CD-01
R01

Workflow automation

Define how source-code changes trigger the delivery workflow. Verify the actual trigger against the repository configuration.

PIPELINE
R02

Build & validation

Identify the configured validation stages, their execution order, and the conditions required before an image is published.

QUALITY
R03

Image distribution

Document the container build process, image registry, tagging strategy, and authentication method used by the workflow.

CONTAINER
R04

Infrastructure & deployment

Establish how Terraform manages infrastructure, how the application reaches Amazon EC2, and how failures are handled.

CLOUD
REQUIREMENTS TO VERIFYR01 — R04
02/ PROBLEM & REQUIREMENTS
ENGINEERING PROBLEM

Define the problem.Engineer the solution.

A reliable delivery pipeline needs a clearly defined path from source-code changes to application deployment. Every stage should have a specific responsibility and verifiable outcome.

01PROJECT OBJECTIVE

Document and evaluate the delivery process across source control, container packaging, infrastructure and cloud deployment.

PROJECT SCOPE
01Source → Workflow
02Build → Registry
03Infrastructure → Deployment

03 / ARCHITECTURE & SYSTEM DESIGN

A pipeline from code to cloud.

The architecture connects source control, automated workflow execution, container image delivery and a cloud-hosted application. Each stage has a distinct responsibility in the delivery process.

CORE TECHNOLOGIES
GitHub Actions Docker Docker Hub Terraform AWS EC2 Flask

Delivery architecture

System flow
01

Source code

Application code and repository changes.

GITHUB
02

Workflow execution

GitHub Actions coordinates configured pipeline jobs.

AUTOMATION
03

Container image

Docker packages the Flask application and its runtime.

DOCKER
04

Image registry

Docker Hub stores the published container image.

DISTRIBUTION
05

Cloud application

AWS EC2 provides the environment for running the application.

RUNTIME

Infrastructure layer

TERRAFORM + AWS

Terraform defines infrastructure resources separately from the application delivery flow. Review the repository configuration to confirm exactly which resources are provisioned and how deployment is triggered.

↳ Diagram represents the system's conceptual flow. Exact job order, trigger conditions and deployment behaviour should match the repository workflow configuration.

04 / IMPLEMENTATION & CORE COMPONENTS

Every component has a job.

The implementation separates application code, container packaging, workflow automation and infrastructure definitions. This structure makes the project easier to inspect, reproduce and maintain.

ENGINEERING PRINCIPLE

Keep application logic, delivery configuration and infrastructure definitions organized separately. Verify the actual workflow and Terraform files before claiming specific tests, deployment triggers or rollback behaviour.

COMPONENT / 01Application

Flask application

The Python application provides the service packaged for deployment. Its source and dependencies live in the application directory.

Source: app/
COMPONENT / 02Packaging

Docker image

The Dockerfile defines how the application environment is assembled into a container image for consistent delivery.

Source: Dockerfile
COMPONENT / 03Automation

GitHub Actions

Workflow configuration coordinates the automated pipeline when its configured trigger conditions are met.

Source: .github/workflows/
COMPONENT / 04Infrastructure

Terraform + AWS

Infrastructure definitions describe the cloud resources used to host the deployed application on EC2.

Source: terraform/
COMPONENT / 05Image storage

Docker Hub

The registry stores container images so the deployment process can retrieve the required application artifact.

Role: Image distribution
COMPONENT / 06Runtime

AWS EC2

The cloud compute instance provides the host environment in which the Dockerized Flask application runs.

Role: Application hosting
05 / WORKFLOW & EXECUTION
DELIVERY LIFECYCLE

From code to cloud.

A delivery pipeline connects source changes to a running application through a sequence of build, packaging, image distribution and deployment activities. Each transition should be traceable and verifiable.

EXECUTION PRINCIPLE

A successful build does not automatically prove a successful deployment. Validate the outcome at each stage and distinguish automated workflow steps from infrastructure tasks performed separately.

EXECUTION SEQUENCE 01 — 05
01

Source change

SOURCE

Application code and its configuration are maintained in the project repository. The configured workflow event determines when automation starts.

GitHub repository
02

Workflow execution

AUTOMATION

GitHub Actions runs the steps defined in the workflow file. Trigger conditions, commands and validation gates must match the repository configuration.

.github/workflows/
03

Container build

PACKAGING

Docker packages the Flask application and its required environment into an image, following the project's Dockerfile.

Dockerfile → image
04

Image distribution

REGISTRY

Docker Hub serves as the image registry in the documented project stack. The actual workflow determines how the image is tagged, authenticated and published.

Docker image → Docker Hub
05

Cloud deployment

RUNTIME

The deployment process delivers the containerized application to its EC2 runtime. Verify the actual deployment commands and confirm the application responds successfully.

Dockerized Flask → AWS EC2
EXPECTED OUTCOME

Application running and verified

VERIFY THE DELIVERY

From workflow to running application.

A CI/CD pipeline needs more than configuration files. Its key stages should be supported by observable project evidence. These artifacts document the workflow result, container image publication, infrastructure output and application access.

01

Workflow execution

The GitHub Actions screenshot records a successful workflow run and completed job.

02

Container publication

The Docker Hub artifact documents the published image tag used in the container workflow.

03

Infrastructure and access

Terraform output and the EC2 browser screenshot document the infrastructure output and application access evidence.

Evidence-led validation Each artifact supports a specific part of the delivery story without treating a single screenshot as proof of every pipeline stage.

ENGINEERING RESPONSIBLY

Reliable delivery. Responsible infrastructure.

Automating deployment also means understanding where credentials live, how infrastructure is exposed, and how failures become visible. This section examines the security and reliability boundaries around the pipeline without assuming controls that have not been verified.

CORE PRINCIPLE

Automate repeatable operations while keeping access, configuration and deployment outcomes reviewable.

RELIABILITY REVIEW 04 / FOCUS AREAS
01
ACCESS CONTROL

Credentials & Secrets

Deployment credentials must be handled separately from application source code. Repository secrets configuration is included in the project evidence; secret values should never be exposed in logs or commits.

PROTECT SENSITIVE VALUES
02
NETWORK BOUNDARIES

Infrastructure Exposure

EC2 security-group rules determine which network connections can reach the instance. Inbound access should be limited to the ports and source ranges required by the application and administration.

REVIEW INBOUND RULES
03
FAILURE VISIBILITY

Workflow Feedback

Workflow status makes the outcome of a run visible. A failed run should be investigated through its available job logs and error output before a new deployment attempt is treated as successful.

INSPECT BEFORE RETRYING
04
INFRASTRUCTURE STATE

Terraform & Change Review

Infrastructure changes should be reviewed before they are applied. Terraform configuration and output provide useful context when checking the intended resources and investigating unexpected results.

REVIEW CHANGES AND OUTPUT

Verification boundary

These are the security and reliability considerations relevant to this stack, not a claim that every control has been implemented or independently tested. No automated rollback, monitoring system or comprehensive security audit is claimed here.

ENGINEERING ANALYSIS / 08

Technology decision matrix

04 COMPONENTS
01 GitHub Actions
02 Docker Build image
03 Docker Hub Image registry
04 AWS EC2 App runtime
INFRASTRUCTURE AS CODE

Terraform defines the AWS infrastructure separately from the application image workflow.

TECHNOLOGY ENGINEERING VALUE TRADE-OFF
01 GitHub Actions

Repeatable workflow execution

Workflow maintenance and debugging

02 Docker

Portable application packaging

Image lifecycle and runtime configuration

03 Docker Hub

Central image distribution

Registry access and tag management

04 Terraform + EC2

Codified infrastructure and a cloud runtime

State, access, capacity and cost management

DESIGN IMPLICATION

Automation reduces repetitive manual steps, but does not remove the need for configuration management, access control, failure investigation and infrastructure oversight.

SYSTEM DESIGN TRADE-OFFS

The stack is a set of engineering decisions.

This deployment pipeline combines workflow orchestration, container packaging, image distribution and cloud infrastructure. The value comes from how these components work together—not simply from selecting individual tools.

A

Separation of concerns

Application packaging and infrastructure provisioning have distinct responsibilities.

B

Repeatability vs. complexity

Automation standardizes steps but introduces workflow and configuration to maintain.

C

Operational ownership

A cloud VM offers control, while its availability, security and upkeep remain responsibilities.

09 / RESULTS & REFLECTION DELIVERY REVIEW

What the pipeline demonstrates.

The project connects workflow automation, container distribution, infrastructure provisioning and application access. Its outcomes are evaluated through the available project evidence—not invented performance metrics.

∴

Engineering takeaway Successful delivery is one milestone. Reliable operation also requires security, observability and recovery planning.

CI/CD DOCKER TERRAFORM AWS EC2
DELIVERY EVIDENCE

Verified project artifacts

04 ITEMS
01
WORKFLOW

GitHub Actions execution

Screenshot records a successful workflow run and completed job.

RECORDED
02
CONTAINER REGISTRY

Docker image publication

Docker Hub screenshot documents a newly pushed image tag.

RECORDED
03
INFRASTRUCTURE AS CODE

Terraform output

Available evidence shows a public IP output from Terraform.

RECORDED
04
APPLICATION ACCESS

Application accessed on EC2

Browser screenshot documents access using the instance IP.

RECORDED
ENGINEERING REVIEW / 01

Lessons & next improvements

L01

Reproducibility

Keep workflows and infrastructure changes version-controlled and reviewable.

L02

Security

Review secret handling, image tags, permissions and network exposure.

L03

Recovery

Define and test recovery procedures instead of assuming automatic rollback.

L04

Observability

Plan application health checks, logs, monitoring and alerting.

PROJECT REPOSITORY PUBLIC REPO
MOMNA-SHAHID17 /

cicd-pipeline-github-actions-terraform

CI/CD Pipeline with GitHub Actions, Docker, Terraform and AWS EC2.

Explore source repository
REPOSITORY STRUCTURE SOURCE MAP
▾ cicd-pipeline-github-actions-terraform/
├─ ▰ .github/workflows/ CI/CD workflow
├─ ▰ app/ Flask application
├─ ▰ diagrams/ Architecture assets
├─ ▰ screenshots/ Implementation evidence
├─ ▰ terraform/ Infrastructure code
├─ ▤ Dockerfile Container build
├─ ▤ README.md Project documentation
└─ ▤ LICENSE MIT license

Selected paths from the repository. Consult GitHub for the complete file tree and current source.

TECHNOLOGY INDEX
GitHub Actions Docker Docker Hub Terraform AWS EC2 Flask / Python
Inspect the implementation Source code, configuration and documentation
PROJECT HANDOFF

Built in code. Documented with evidence.

The repository brings together the application, workflow configuration, infrastructure code, diagrams, screenshots and project documentation. It provides a starting point for reviewing how the delivery pipeline is assembled.

01

Inspect the workflow

Review the GitHub Actions configuration and delivery steps.

02

Review the infrastructure

Explore the Terraform files and their role in AWS provisioning.

03

Follow the evidence

Compare repository artifacts with the documented workflow and deployment results.

POTENTIAL NEXT ITERATIONS
+

Add automated application and deployment health checks.

+

Improve operational monitoring and failure visibility.

+

Evaluate deployment recovery, scaling and security controls.

These are potential future improvements, not claims that the capabilities are already implemented.

Scroll to Top