|
|
|
|
|
by nunez
1078 days ago
|
|
You can totally do that. You can even run localstack on both machines to have mocks of AWS services that you can use the AWS CLI against. You can even run Kubernetes on your nodes and run whatever you need on them. Plenty of folks do that; check out the homelab scene. I personally don't because it costs me $5/mo to run several "serverless" functions via API gateways that communicate through message queues, some on a schedule, host some websites with globally-accessible DNS records and hold a ton of backups for stuff I care about, without me having to do a ton of systems administration to keep the lights on. (Most of the cost is DNS, actually! Everything else falls within free tier limits. Genius move on AWS's part, as I know AWS well and have recommended it to several large companies; they've made their money from me for sure) I did that back in the day (ran my own email server). I'd rather do other things with my time now. |
|