Cloud engineer · AWS architect · 5× certified
Building secure, scalable cloud platforms that help enterprise teams move with confidence.
Selected focus
I bring hands-on cloud engineering and AWS architecture to complex enterprise challenges—translating security, scale, and operational needs into platforms teams can use and evolve. My focus includes cloud architecture, automation, infrastructure as code, and practical technical learning.
Credentials
Professional
Expires Aug 6, 2028
Associate
Expires Aug 6, 2028
Foundational
Expires Aug 6, 2028
About
I’m an experienced Cloud Engineer and AWS Architect at Caterpillar, where I focus on secure, scalable, and cost-conscious solutions for enterprise workloads. I’m drawn to the intersection of sound engineering and useful outcomes: technology should make a business more capable, not more complicated.
My work spans AWS architecture, Python automation, Linux, Docker, Terraform, CloudFormation, and configuration automation. I hold five AWS certifications and a degree in Computing and Information Systems from the University of London.
I also write about practical engineering topics, including cloud-native systems, local-first applications, and AI developer tools. I enjoy sharing what I learn and keeping a hands-on perspective as the technology landscape evolves.
How I work
Strong cloud platforms are the result of deliberate trade-offs. I help teams turn business goals, security requirements, and operational realities into AWS environments that are understandable to operate and ready to evolve.
The work often begins with careful discovery: understanding the workload, its dependencies, the team’s delivery process, and the constraints that matter most. From there, I prefer small, observable improvements over unnecessary complexity—establishing a secure baseline, automating repeatable tasks, and leaving each system clearer for the next engineer. This approach keeps cloud decisions grounded in evidence, gives stakeholders a clear view of risk, and creates momentum without sacrificing quality.
I design cloud architectures around the workload, its users, and the people responsible for it after launch. That means choosing managed services where they simplify operations, separating concerns clearly, and making availability, recovery, performance, and cost visible choices rather than late-stage surprises.
For enterprise AWS workloads, good architecture is more than a diagram. It gives teams a dependable path from an idea to a production service, with room to grow without rebuilding the fundamentals.
Security works best when it is part of the platform rather than a checklist added after delivery. I focus on identity and access, network boundaries, encryption, secrets handling, logging, and auditability so that teams can move quickly within useful guardrails.
Infrastructure as code with Terraform and CloudFormation makes those foundations repeatable. It also makes reviews, change history, and recovery more reliable—important qualities when an environment supports real customers and business operations.
I use Python, Linux, Docker, CI/CD, and configuration automation to remove the work that should not require a human every time. The aim is not automation for its own sake; it is faster feedback, safer releases, and more time for engineers to solve meaningful problems.
Clear runbooks, observable services, and practical documentation keep automation useful long after it is written. They help teams diagnose issues calmly, improve systems incrementally, and share knowledge instead of creating bottlenecks.
Cloud engineering changes quickly, so I keep learning in public as well as on the job. My Lankan Lion Blog collects practical notes on cloud-native systems, local-first software, AI developer tools, and experiments worth carrying into day-to-day engineering. The goal is simple: stay curious, test ideas carefully, and turn useful lessons into platforms that help people do their best work.
Whether the work is a new AWS foundation, a delivery pipeline, an operational improvement, or a technical question that needs an honest answer, I value practical collaboration. Good platforms make the safe and useful path the easiest path for the teams who rely on them.
Start a conversation
Whether you’re exploring cloud architecture, automation, or a new product idea, I’d be glad to hear from you.