AWS
Welcome to re:Invent 2020 and see you in Neon City
· β˜• 4 min read · ✍️ Sathya
November end/December is a fairly exciting time for a lot of AWS enthusiasts - it’s time for re:Invent, AWSs’ annual event which brings in tens of thousands of AWS users, enthusiasts, power users, customers and more. For the AWS Heroes, it’s also the time to get together, talk, mingle, discuss and debate on all things AWS and more. It’s the time where we pack our bags and head off to Las Vegas.

Running Folding@Home on AWS with AWS CDK
· β˜• 3 min read · ✍️ Sathya
Folding@Home(aka FAH) is a distributed computing project. To quote from their website, FAH is a distributed computing project for simulating protein dynamics, including the process of protein folding and the movements of proteins implicated in a variety of diseases. Folding@Home involves you donating your spare computing power by running a small client on your computer. The client then contacts the Folding@Home Work Assignment server, gets some workunits and runs them, You can choose to have it run when only when your system is idle, or have it run all the time.

At AWS re:Invent 2019
· β˜• 2 min read · ✍️ Sathya
I’ve always dreamed of being at reInvent and this year, not only do I get to be at re:Invent, I also get a chance to lead a Dev Chat. I’m really excited to be there, to present and more importantly, to meet and interact with other AWS Heroes and re:Invent participants. Last year, I was honoured to being named as one of the Community Heroes and almost made it to re:Invent 2018.

DevOps Diaries: When Terminator terminates your MySQL imports onto an AWS Instance…
· β˜• 3 min read · ✍️ Sathya

I have begun to use Terminator quite a lot. Terminator’s quite handy when you want to connect to multiple servers on a single terminal thanks to its split pane feature. (And yes I know about tmux & screen - I have screen on my servers, don’t want to get into the headache that is nested screen panes).

Few days back we were preparing for a big migration & deploy and I was tasked upon to prepare a failover just in case the migration goes wrong. I have an automated daily backup from prod and restore to local server, I decided to restore from the MySQL dump on the local server onto the AWS instance via the automated process. Since database restores can take a bit of time, I started the restore and went over to grab some coffee. Once back, I noticed that the import was done and proceeded with a rake db:migrate and realized that rake was doing a migration going all the way back from the start… that did not look proper.