In partnership with
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 FUTUREPEDIA
2 Free AI Courses. No Credit Card Needed.
5,000+ professionals use Skill Leap to get ahead with AI. Right now, two of their best courses are completely free - Claude 101 and the 14-Day AI Boot Camp.
Claude 101 covers prompting frameworks, Artifacts, file analysis, and real-world workflows in 19 lessons.
The Boot Camp covers ChatGPT, Gemini, Midjourney, and prompt engineering in 16 lessons. Downloadable workbooks. LinkedIn certificate.
Zero cost, no credit card, no catch.
IN TODAY'S EDITION
🧠 Use Case
How AWS Secures Inbound and Outbound Network Traffic
👀 Remote Jobs
Your Software Supplier is hiring a DevOps Engineer
Remote Location: Worldwide
Anagram is hiring a 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:
🧠 USE CASE
How AWS Secures Inbound and Outbound Network Traffic
AWS Security Groups (SGs) are stateful firewalls controlling inbound and outbound traffic at the instance level. Security Groups attach directly to EC2 instances, RDS, ALB, Lambda (in VPC), etc.
By default:
All inbound traffic is blocked. You must explicitly allow it.
All outbound traffic is allowed. Unless you restrict it.
Since SGs are stateful, if an inbound request is allowed, the response is automatically allowed (you don’t need an outbound rule for responses)
Every rule in a Security Group has the following technical parameters:
Security Groups can reference other Security Groups instead of IPs. This is critical when working with multiple tiers (Load Balancer → App Server → Database)
Use Case: ALB to Web Server
Instead of exposing your Web Server to
0.0.0.0/0, allow only traffic from the ALB’s SG.This way, only traffic from the ALB is allowed.
Why? If the ALB’s IP changes, the rule still works because it references an SG dynamically.
Debugging Security Group Issues
1. Check Security Group Rules
aws ec2 describe-security-groups --group-ids sg-12345678Look for missing rules if traffic isn’t working.
2. Check if the Instance is Associated with the Right SG
aws ec2 describe-instances --query 'Reservations[].Instances[].SecurityGroups'An instance can have multiple Security Groups, ensure the right one is attached.
3. Use VPC Flow Logs to Detect Blocked Traffic
If traffic never reaches your instance → Wrong Security Group rule.
If the request reaches but gets no response → Application issue.
Things to Remember:
Use Security Groups, not static IPs in rules.
Avoid “allow all” rules (0.0.0.0/0) unless necessary.
Don’t allow 0.0.0.0/0 inbound for SSH or databases.
Use IAM roles for permissions, not security groups alone.
Regularly audit SGs to remove unused or overly permissive rules.
Only allow necessary ports (e.g., SSH from a trusted IP, HTTP from the internet).
🔴 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.
