Portfolio
Cloud Infrastructure for a Confidential B2B Fintech Platform
Modernized AWS infrastructure for a confidential B2B fintech platform to improve availability, compliance controls, multi-environment workflows, and cost efficiency.
AWS
Kubernetes
Fintech
Compliance
Key challenges
- Limited observability and alerting across services.
- Manual, error-prone Kubernetes deployment workflows.
- Fragmented infrastructure without standardized networking primitives.
- Inefficient Jenkins workflows with manual UI steps.
- Low reuse across Kubernetes service deployments.
Outcomes
- Centralized logging, metrics, and alerting for EKS workloads.
- Secure, scalable networking aligned to AWS best practices.
- Reusable Helm charts that simplified multi-service releases.
- Codified Jenkins pipelines with clear environment separation.
- Reduced deployment errors by removing manual UI steps.
Architecture + observability
A high-level snapshot of the observability stack used to standardize logging and alerting for EKS workloads.
My contributions
- Built the observability stack with CloudWatch Agent, Fluent Bit, and custom dashboards with alerts.
- Designed the networking layer (VPC, subnets, route tables, security groups).
- Moved EKS deployments to pure YAML workflows, reducing reliance on
kubectl. - Implemented Helm to standardize and template multi-service deployments.
- Deployed Jenkins Cloud using Kubernetes as dynamic build agents.
- Refactored Jenkins pipelines into codified Jenkinsfiles with audit-ready separation.
Technologies used
- Infrastructure as Code: Terraform (modular).
- CI/CD: Jenkins (Kubernetes Cloud, Jenkinsfiles), GitHub Actions.
- Cloud Provider: AWS (EKS, RDS, ALB, CloudWatch, IAM, Secrets Manager).
- Kubernetes Management: Helm, kubectl, YAML-based manifests.
- Monitoring: CloudWatch Logs, Metrics, Dashboards, Fluent Bit.
Let's connect
Reach out for collaboration, roles, or advisory work.
