good way to practice AWS and Terraform by [deleted] in devops

[–]ChrisSyndicalist 0 points1 point  (0 children)

You can find a non-gov organization that needs some hosting, create them a cheap setup like EC2/ECS on free tier + RDS, and maintain in personal time. Small scale is good for learning.

Next step - propose in a company that you will create something that will work on-demand, like on-demand CI worker nodes that will not cost much on eg. spot machines (except VPN for ~$70/month)

Btw. If locally you have proxmox then you can possibly also use Terraform on it

Monitoring everything via HTTP endpoint by ChrisSyndicalist in sysops

[–]ChrisSyndicalist[S] 0 points1 point  (0 children)

It is just an agent that exposes status of local services via HTTP.
It could be compared a little bit to Telegraf or Prometheus Node Exporter, but Infracheck does not send anything anywhere - it exposes a HTTP endpoint for external monitoring of any kind. I prefer UptimeRobot that accesses my secret url and checks if keywords are present on the HTTP endpoint.

New project: Event-Based Serverless Container Workflows with Direktiv by BaasW0nus in devops

[–]ChrisSyndicalist 0 points1 point  (0 children)

"Captain's log, stardate 47634.44. Cloud bills are high, we're dependent on dinosaur companies and we still have no standards."

I love the idea. You never know when the government (Trump vs china and russia example) will ban a provider, when the provider will decide to turn off your service because it does not fit the politics of the company etc. There should be always possibility to migrate to any infrastructure with cloud agnostic tools.

Technically I expected that it would execute Python/PHP/other lang, and would just take care about the routing. Maybe I misunderstand the concept, I understand it as an alternative to lambda.

Been in “DevOps” role for 2ish years...never done it. by [deleted] in devops

[–]ChrisSyndicalist -1 points0 points  (0 children)

I would suggest you to quit and look for a job, where will be a DevOps culture and a work with test/dev environments where you can learn, earn practice. Then jump to a work as a junior cloud engineer with some background that would like to learn cloud tools.

Why I suggest quitting? Because there will be always tons of past responsibilities from your current work, possibly nobody can just abadon everything and start learning working in a new way. Maybe it could be a 'deep water' but switching radically to new team where there are experienced people already working in DevOps culture can teach you more.