Architecting chaos into order on AWS, GCP & Azure,
I build scalable infrastructure and cut cloud costs with FinOps,
Bridging the gap between Code and Ops.
Some players win trophies while some win the hearts, @neymarjr you did both, even if the world cup never came home ππ
You carried a nation dreams every time you wore yellow jersey, Thank you for the magic and making millions fall in love with football.
Obrigado, Ney π§π·β₯οΈπ
BYE-BYE POWERPOINT.
Claude 4.7 just made presentations obsolete.
In 60 seconds, it builds slides better than most professionals.
Here are 6 prompts that do everything for you π
π Save this before everyone starts using it.
My biggest achievement over the last few months? Slicing the AWS bill by nearly 50%!
Nothing beats the thrill of seeing those costs drop while keeping our cloud performance top-notch. So incredibly proud of this win!
#AWS#FinOps#DevOps#CostOptimization#CloudOps
3οΈβ£ The Weekend Wipe: A secondary cron runs every Friday night to sweep remaining idle resources before the weekend.
Build systems that clean up after themselves. π§Ή
#FinOps#DevOps#SystemDesign#Automation#CloudComputing
Day 6/90: The silent killer of cloud budgets? Forgotten environments.
Devs and QAs are busy shipping features. Expecting them to manually delete their test environments is a failing strategy.
System Design Rule: Automate the garbage collection.
Today, I finalized the lifecycle automation for our Ephemeral Environments:
1οΈβ£ Age: 3 Days.
2οΈβ£ The Daily Sweep: A cron job runs daily at 00:00 UTC. It checks the age of all environments. If > 3 days, it auto-triggers our POST /delete API.
The API iterates through the list, validates ownership for each item, and triggers the destruction pipeline.
Code is live: https://t.co/3Pix7zdx3r
Clean infrastructure = Happy wallet. π°
#DevOps#FinOps#Python#FastAPI#CloudNative
The Feature:
I didn't want to delete environments one by one. Thatβs tedious. I built a Bulk Delete endpoint that accepts a List[str].
The Logic: POST /deletePayload: ["eph-1", "eph-4", "eph-9"]
Day 3/90: The Heart of the System: The Create Endpoint.
Today, I pushed the core logic for spinning up ephemeral environments.
The Logic:The POST /create endpoint takes your feature branches (frontend / backend) and maps them to a new environment.
Day 3/90: The Control Plane is taking shape.
Today, I built the core /list endpoint for the Ephemeral Environment system.
Using FastAPI and the Kubernetes Python Client, this function queries the cluster directly to fetch real-time status of all active environments.
Over the next couple of Days, I am designing a system to automate this:
1οΈβ£ Isolation: Every PR spins up a dedicated K8s namespace.
2οΈβ£ Replication: A lightweight, ephemeral copy of Production (DB + App + LB).
3οΈβ£ Destruction: Resources vanish when the PR closes.
Testing in a "dirty" shared environment produces false negatives and kills developer velocity.
The Architectural Fix: Ephemeral Environments.We need to move from Static Shared State β‘οΈ Dynamic Isolated State.