TechOps Examples
Hey — It's Govardhana MK 👋
Welcome to another technical edition.
Every Tuesday – You’ll receive a free edition with a byte-size use case, remote job opportunities, top news, tools, and articles.
Every Thursday and Saturday – You’ll receive a special edition with a deep dive use case, remote job opportunities and articles.
👋 👋 A big thank you to today's sponsor TIGER DATA
Your events table just 10x’d its row count
Every login, every API call, every sensor reading is now a timestamped event, and your Postgres tables are growing faster than ever. Queries creep up. Dashboards drag. The usual next step is a second database.
Tiger Cloud keeps you on Postgres: hypertables partition as data piles up, compression cuts storage by up to 95%, and continuous aggregates keep usage dashboards live.
👀 Remote Jobs
Supabase is hiring a Cloud Platform Engineer
Remote Location: Worldwide
Replicant is hiring a Senior Site Reliability Engineer
Remote Location: Worldwide
📚 Resources
If you’re not a subscriber, here’s what you missed last week.
To receive all the full articles and support TechOps Examples, consider subscribing:
🛠 TOOL OF THE DAY
git-graph - Command line tool to show clear git graphs arranged for your branching model.
🧠 USE CASE
AWS VPC Flow Logs Architecture Explained
In real world environments, VPC Flow Logs are often enabled at the subnet or VPC level to monitor traffic across critical infra. Teams forward logs to a centralized S3 bucket for long term retention and to CloudWatch Logs for real time alerting and investigations. This setup helps security teams detect suspicious connections, investigate denied traffic, and validate firewall rules. It also supports compliance audits by providing a clear trail of all accepted and rejected network flows within the VPC.
VPC Flow Logs capture IP traffic going to and from network interfaces in your VPC. These logs help you understand network behavior, troubleshoot connectivity issues, and monitor for suspicious activity.
VPC Flow log Breakdown
A typical VPC Flow Log infers:
Who initiated the connection: Source IP and port (srcaddr, srcport)
Who received it: Destination IP and port (dstaddr, dstport)
What kind of traffic it was: Protocol such as TCP (6)
How much traffic flowed: Packets and bytes
When it happened: Start and end timestamps
Whether it was allowed or blocked: action (ACCEPT or REJECT)
If logging succeeded: status (OK or error)
Real World Scenarios Using VPC Flow Logs
1. EC2 Instance Not Reachable via SSH
You launch a new EC2 instance but cannot SSH into it. Flow logs show no entries from your IP, which means traffic is not reaching the instance, likely due to a missing inbound rule or incorrect routing.
Action: Check the security group for port 22 access, verify route table and NACLs, and confirm public IP assignment.
2. Unexpected Data Transfer
You notice a spike in AWS data transfer costs. Flow logs show a specific EC2 instance sending large volumes of outbound traffic to an unknown IP. Possible data exfiltration or misconfigured process.
Action: Quarantine the instance, investigate the process, and block the external IP at the network layer.
3. Connectivity Debugging
Internal users report intermittent timeouts when accessing an internal API. Flow logs show ACCEPT entries but with unusually low packet counts. Connections are accepted but not completing, possibly due to app timeouts or dropped responses.
Action: Check application logs, inspect client behavior, and correlate with flow log timestamps.
🔴 Get my DevOps & Kubernetes ebooks! (free for Premium Club and Personal Tier newsletter subscribers)
Looking to promote your company, product, service, or event to 50,000+ DevOps and Cloud Professionals? Let's work together.
