{{ logToggle }} session.log · for the technical: try help
clear
tl@ops:~$ {{ h.cmd }}
{{ o.text }}
NEW HERE?
Not technical? Just scroll. Each section has a plain line under the command.
tl@ops:~$ whoami
Who I am and what I actually do.
Hoon Thean Loon_
{{ typed }}
I make AWS cost and usage easy to see, and automate the reporting so nobody does it by hand. Before cloud, six years shipping games and the services behind them.
AWS · Lambda · Step Functions
Athena · Glue · QuickSight
Python · SQL · TypeScript · C#
CloudWatch · OAM · IAM · VPC
aws sts get-caller-identity
- UserId
- TL
- Role
- SolutionsArchitect
- Org
- GoShare / Skybit Cloud
- Region
- Kuala Lumpur, MY
- Langs
- EN · 中文 · BM · 粵
- Status
- open_to_work=true
tl@ops:~$ cloudwatch get-metric-data --namespace TL/Career
The numbers, at a glance.
tl@ops:~$ ls ~/projects --sort=impact
Things I built and what changed because of them.
01 · COST & USAGEQuickSight · Athena · Lambda
Multi-account cost dashboard
One view of spend, usage and trend across every account and service. Leadership reads it directly, no raw exports.
› Replaced manual monthly spreadsheets
02 · AUTOMATIONEventBridge · Step Functions
Scheduled reporting pipeline
CRON→PREP→QUERY→REPORT→SEND
Data prep, queries and report generation run on a schedule with retries and an audit trail. Same output every time.
› Hours of repeat work per week, now zero
03 · OBSERVABILITYCloudWatch · OAM
Cross-account monitoring
Metrics and logs from every account flow into one place, so services can be compared side by side.
› One console instead of one login per account
Also: architecture diagrams, TCO models and implementation docs for AWS partner engagements.
tl@ops:~$ tail -n 3 /var/log/experience.log
Work history, newest first.
{{ r.from }}
↓ {{ r.to }}
{{ r.tag }}
{{ r.title }}
{{ r.org }}- ›{{ b }}
{{ r.stack }}
{{ rolesToggle }}
tl@ops:~$ watch -n 1 ./pipeline --live
How the automation works. Raw data goes in on the left, a finished report comes out on the right, no hands in between.
tl@ops:~$ describe-stack --name multi-account-reporting
How a typical system I build fits together. Live view: packets move, resources report healthy.
Reference build: cost, usage and ops reporting across AWS accounts
STACK_STATUS: CREATE_COMPLETE · {{ resCount }}/10 healthyCollect from many accounts, transform on a schedule, show it as dashboards.
LANE A · DATAdata in, charts out.
{{ n.svc }}
{{ n.name }}
{{ n.note }}
LANE B · AUTOMATIONscheduled jobs replace manual reporting.
{{ n.svc }}
{{ n.name }}
{{ n.note }}
{{ o.k }}. {{ o.v }}
tl@ops:~$ top -o proficiency
Skills and how long I've used each.
{{ g.title }}{{ g.meta }}
{{ s.n }}{{ s.y }}
{{ s.pct }}
tl@ops:~$ ls -la ~/credentials
Certifications and education. Click to verify.
SAA
VERIFIED · CREDLY
AWS Certified Solutions Architect – Associate
Amazon Web Services · click to verify badge ↗
GenAI
TRAINING BADGE
AWS Partner: Generative AI Technical
AWS Partner Network · accredited
B.Sc
EDUCATION · DOUBLE DEGREE
TARUC × Campbell University (USA)
Game & Interactive Media Design · CGPA 3.72 / 3.56
tl@ops:~$ git log --oneline shipped/ | head -4
Proof I ship: six years of released software before cloud.
10+ titles shipped · led a mini-game studio on reusable templates (new title in ~1 week) · full game portfolio ↗
tl@ops:~$ ssh recruiter@hire-tl
Get in touch.
Connection established. Let's build something that runs itself.
Open to cloud, solutions-architecture and software-engineering roles · Kuala Lumpur or remote.
+60 16-219 9826 · Kepong, Kuala Lumpur, Malaysia
© 2026 HOON THEAN LOON{{ achievementsLine }}