Step 01
Start local services
docker compose up -dREAL AWS CLOUD PROOF
Real AWS cloud data engineering proof project using EventBridge Scheduler, ECS/Fargate, S3, Redshift Serverless, dbt, and CloudWatch Logs to run a scheduled batch pipeline from flight API ingestion to analytics-ready marts.

Local validation
Docker + Postgres
Proven AWS path
Scheduler → ECS/Fargate → S3 → Redshift
Orchestration
EventBridge + CloudWatch
Modeling
dbt marts + tests
Reviewer proof
Screenshots, logs, SQL, CI
AWS Proof Diagram
Real AWS execution path showing how EventBridge Scheduler triggers an ECS/Fargate batch container to ingest flight data, land raw data in S3 Bronze, load Redshift Serverless, build dbt staging/marts/tests, and capture execution proof in CloudWatch Logs.

LOCAL VALIDATION PATH
Run the project locally with Docker, Postgres, dbt, and proof queries before reviewing the AWS proof path.
Step 01
Start local services
docker compose up -dStep 02
Load sample fares
python scripts/load_sample_to_postgres.pyStep 03
Build dbt models
dbt build --project-dir dbt/flight_fares --profiles-dir dbtStep 04
Run proof queries
python scripts/run_analysis_queries.pyExecution paths
The project is easiest to review through two paths: a reproducible local validation path and a proven AWS execution path. Both produce dbt-modeled marts and analytics-ready SQL outputs.
marts.fact_fares, marts.dim_route, and marts.dim_date.TECHNICAL ARCHITECTURE
Detailed repository architecture showing ingestion, raw/bronze landing, cleaned processing, dbt modeling, validation, and analytics outputs.

Analytics-ready outputs
The project goes beyond ingestion and modeling by documenting marts, SQL query patterns, and downstream handoff artifacts reviewers can inspect after the pipeline runs.
SQL output examples

Static downstream handoff artifact for reviewer inspection, not a live hosted BI app.
Execution Proof
Reviewer evidence is surfaced here instead of hidden behind link lists. These proof assets show the AWS scheduler, ECS/Fargate execution, CloudWatch success logs, Redshift/dbt validation, S3 Bronze landing, and local validation support.

Scheduler configuration showing the AWS batch trigger path for the Fargate job.

Containerized batch run completed successfully in ECS/Fargate.

CloudWatch log evidence showing the scheduled AWS run completed successfully.

Warehouse proof showing Redshift loading and dbt build validation.

S3 storage proof showing dated fare snapshots under the Bronze path.

Local Airflow graph showing the load, dbt build, and proof-query chain.
Start with the Current Proven AWS Path diagram, then review the AWS proof assets, local validation path, and downstream outputs. This page separates cloud proof, local validation, and reviewer handoff without overclaiming a live production service.