Bouchraya Kory | Cloud & DevOps Engineer

About Me & Why I Chose Cloud

My path into Cloud Engineering comes from a strong analytical and operations engineering background at Meta. Experiencing firsthand how legacy IT architectures create operational friction made me fall in love with AWS and cloud-native computing.

Treating infrastructure strictly as code empowers me to build reliable systems that scale on-demand, self-heal under load, and maintain robust security standards automatically.

Strengths & What I Offer Your Organization

My Key Strengths

Infrastructure as Code Mindset: Committed to managing 100% of resources declaratively using Terraform to eliminate configuration drift.
Pragmatic Problem Solver: Experienced in systematically diagnosing complex failures across CDNs, load balancers, security groups, and containers.
Automation-First Approach: Focused on hands-off CI/CD pipelines that automate linting, building, image pushing, and deployments safely.
Continuous Learning: Rapidly adapting to emerging cloud technologies, tools, and architectural patterns.

What I Can Provide to Any Team

Reliable Deployments: Production-ready CI/CD pipelines that reduce manual effort and speed up release cycles.
Cost Optimization: Ability to weigh architectural trade-offs (e.g., Serverless Lambda vs. ECS Fargate vs. EC2) to balance performance against AWS cost.
Enhanced Security Posture: Implementation of least-privilege IAM policies, secure CloudFront origin access control (OAC), and isolated networking.
Clear Documentation & Ownership: Detailed architecture diagrams, complete READMEs, and strong operational accountability.

Cloud Architecture & DevOps Engineering Showcase

System Architecture Topology

Client Browser

AWS CloudFront CDN

HTTPS / Multi-Origin Router

Serverless API: API Gateway ➔ AWS Lambda ➔ DynamoDB

Container VPC: ALB (Public Subnet) ➔ ECS Fargate (Private Subnet)

Static Host: S3 Bucket (Private Access via OAC)

Cloud Resume Challenge (Hybrid Serverless & Containers)

Production-grade infrastructure managed 100% declaratively via Terraform and automated via GitHub Actions.

1. Network Topology: Custom VPC & Multi-AZ Subnets

Services Used: AWS VPC (Custom CIDR 10.0.0.0/16), 2x Public Subnets, 2x Private Subnets, Internet Gateway, Route Tables, Security Groups.

Why Custom VPC Over Default AWS VPC?
Default AWS VPCs (172.31.0.0/16) use flat public subnets across all instances. To enforce zero-trust security principles, I created a custom VPC (10.0.0.0/16) spanning 2 Availability Zones. Public subnets host only external entry points (ALB), while private subnets host containerized tasks (ECS Fargate) without direct public IP address allocation.

2. Serverless Layer: AWS Lambda & DynamoDB

Services Used: AWS Lambda (Python Runtime), Amazon API Gateway (HTTP API), Amazon DynamoDB, IAM Roles (Least Privilege).

Why AWS Lambda for Visitor Counter?
Running dedicated server compute 24/7 for low-frequency counter updates incurs idle costs. I built an event-driven Python Lambda function triggered via API Gateway. Lambda executes atomic counter updates (ADD views :inc) directly on DynamoDB in single-digit milliseconds and scales down to zero instantly—costing /usr/bin/bash when idle.

3. Compute Layer: ECS Fargate Containers & ALB

Services Used: AWS ECS Fargate, Amazon ECR, Application Load Balancer (ALB), Target Groups, Health Checks.

Why ECS Fargate Over EC2?
Chose serverless container orchestration (Fargate) to eliminate manual EC2 instance provisioning, OS security patching, and capacity planning. Containers run inside isolated VPC private subnets, receiving traffic strictly forwarded from the ALB on Port 5000.

4. Real-World Engineering Challenges & Fixes

Challenge 1: CORS & Mixed Content Errors
Problem: Browser security blocked HTTPS calls from CloudFront to an unencrypted HTTP ALB endpoint.
Solution: Configured CloudFront with dual origin paths ( to S3 and to ALB) to route all backend container traffic through a single unified HTTPS CDN domain.

Challenge 2: CDN Edge Cache Invalidation
Problem: Uploading new static assets to S3 didn't update the site immediately due to CloudFront edge caching.
Solution: Scripted automated cache invalidation commands () into Git Bash and CI/CD scripts post-sync.

5. Cost Optimization & ROI Analysis

Architecture Model	Est. Monthly Cost	Operational Efficiency & Trade-offs
Traditional EC2 Monolith	~5.00 - 0.00	Pays for idle server capacity 24/7; requires manual OS patching & server management.
Pure ECS Fargate Setup	~8.00 - 5.00	Zero OS management, but incurs steady running costs for continuous container tasks.
Our Hybrid (Lambda + Fargate)	~.00 - .00	/usr/bin/bash base cost on serverless Lambda + optimal container utilization & high availability.

Live Infrastructure Telemetry

AWS Lambda Visitor Counter Views: Loading...

ECS Fargate Container API Status: Connecting...

Custom VPC CIDR 10.0.0.0/16 (Isolated)

Tech Stack & Tools

Deployment Method Deployed via Git Bash using Infrastructure as Code (Terraform) and automated CI/CD pipelines.

Work Experience & Education

Fiber Operations Support Engineer

Operations Analyst

Education & Credentials

AWS Certified Solutions Architect – Associate Course

AWS Training & Certification (2026) Comprehensive study of high-availability, fault-tolerant, and cost-effective multi-tier AWS architectures.

Bachelor of Science (B.Sc.)

University (2018) Strong foundation in scientific principles, analytical problem solving, and quantitative data analysis.

Technical Skills & Languages

AWS & Serverless

AWS Lambda, API Gateway, DynamoDB, Custom VPC, CloudFront, S3, ECS Fargate, ALB

Infrastructure as Code

Terraform, HCL Modules, State Management, Git Bash Automation

Containers & CI/CD

Docker, Amazon ECR, GitHub Actions Workflows

Development

Python (Lambda Boto3), Flask REST APIs, JavaScript, Bash Scripting

Languages

Spanish (Native) Arabic (Native) English (Professional / High Level)

Hi, I'm Bouchraya Kory