I'm Muhammad Ashraf Bin Johari, an engineer with experience in software, APIs, databases, hardware integration, AWS Cloud, and self-hosted infrastructure.
I'm currently focused on AWS Cloud Infrastructure, Operations and Observability.
I'm also building hands-on networking skills with Cisco technologies, including TCP/IP, switching, routing, VLANs, subnetting, and network connectivity.
My engineering background started with software development and system integration.
Over time, my work expanded into APIs, middleware, databases, hardware integration, monitoring and self-hosted infrastructure.
Cloud engineering became the natural next step: combining software engineering with networking, compute, databases, security, automation and observability.
My current AWS project focuses on understanding not only how to deploy infrastructure, but also how to operate and troubleshoot it.
A combination of cloud infrastructure, software engineering, systems integration and operational technologies.
EC2 • ALB • RDS • S3 • VPC • IAM
CloudWatch • Logs • Metrics • Resource Monitoring
Cisco • TCP/IP • Switching • Routing • VLAN • Subnetting • DNS • Linux • Windows
API Gateway • Lambda • AWS SDK • REST APIs
C# • .NET • Python • REST API
MySQL • RDS • Data Integration
TrueNAS • Nextcloud • Cloudflare
Middleware • RFID • Hardware • APIs
My AWS learning focuses on building and operating connected infrastructure rather than learning individual services in isolation.
Application hosting using multiple EC2 instances, nginx, security groups and operational monitoring.
Application Load Balancer used to distribute HTTP/HTTPS traffic across application servers.
Managed MySQL database supporting the application infrastructure.
Monitoring metrics and logs to understand infrastructure health and application behaviour.
Serverless operations API used to retrieve AWS infrastructure and monitoring information for the dashboard.
AWS cost information integrated into the operations platform for infrastructure visibility.
The dashboard is more than a static portfolio page. It connects to AWS through a serverless operations API and displays information about the actual cloud environment.
Retrieves AWS resource information through the operations API and presents resources such as EC2 instances in the dashboard.
CloudWatch information provides visibility into metrics, logs and operational status.
AWS Cost Explorer data can be exposed through the operations API to provide infrastructure cost awareness.
API Gateway exposes operational endpoints backed by Lambda, allowing the frontend to retrieve AWS information without directly exposing AWS credentials.
The current production-style architecture separates application traffic from operational management and observability.
Building the infrastructure taught me that cloud engineering is also about monitoring, diagnosing failures, understanding network paths and maintaining operational visibility.
One of the most valuable parts of the project has been diagnosing connectivity and infrastructure problems instead of treating AWS as a collection of buttons.
Investigated unhealthy EC2 targets and traced the traffic path from the Application Load Balancer to nginx and the application.
Worked through the difference between the ALB health-check port, nginx listening on port 80 and the application running on port 8080.
Configured domain routing through Cloudflare and investigated DNS, SSL and origin connectivity issues.
Built and debugged the path between the dashboard, API Gateway, Lambda and AWS service APIs.
Integrated AWS resource information into the dashboard so infrastructure can be viewed dynamically rather than using hard-coded values.
Connected AWS Cost Explorer information to the operations layer to make infrastructure cost part of operational awareness.
My goal is to combine my existing experience in software development, API integration, middleware and infrastructure with hands-on AWS experience. I want to build, troubleshoot, monitor and continuously improve reliable cloud environments.