Search for a command to run...
Series
Here we only discuss about how to implement AWS for DevOps.
Welcome to Day 28 of our 30-Day AWS DevOps Series! We have entered the final stretch: Phase 5 (Observability, Security & Best Practices). Over the last four weeks, you've built pipelines, deployed con
Yesterday, we shined a light on our cluster metrics using Prometheus and Grafana. We learned if something is broken. But when an API throws a 500 Internal Server Error, metrics won't tell you the exac
In a monolithic application, tracking down a bug usually means logging into one server and running tail -f var/log/app.log. But in a Kubernetes cluster with hundreds of ephemeral pods constantly movin
Yesterday, we learned how to package our Kubernetes applications using Helm. But how do we actually deploy and update them automatically when our code changes? Enter GitOps and ArgoCD — the modern sta
By default, Kubernetes Pods are "stateless." If a Pod dies, any data saved inside its container is lost forever. For databases or file uploads, this is a nightmare. Today, we solve this by diving into
Yesterday, we learned about Services. But if you have 20 microservices, do you really want to create 20 separate Cloud Load Balancers? (Spoiler: Your AWS bill says "No"). Welcome to Kubernetes Ingress
